ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert" <boisv...@intalio.com>
Subject Re: WSDL import error on wsdl generated by weblogic workbench
Date Thu, 05 Jul 2007 17:32:47 GMT
Hi Dan,

The first schema definition requires a <xsd:import> to reference types from
a different namespace.

    <xs:schema attributeFormDefault="unqualified"

        <xs:import namespace="java:com.thisprogram.beans"/>



On 7/5/07, Dan <leutnant.dan@gmail.com> wrote:
> Hi,
> A service provider generated a wsdl using weblogic workbench.  The bpel
> compiler generates errors attempting to parse the file.  (I've included a
> sanitized version of the wsdl).
> The problem may be the use of a namespace inside the type declarations
> which differs from the target namespace of the wsdl.  I'm not sure if BEA's
> tool is out of spec here, or if bpelc does not account for this condition.
> (I am able to get the wsdl to import if I collapse the two schema blocks
> into one and unify the namespaces.)
> ping]$ /opt/apache-ode-jbi-1.0-incubating/bin/bpelc.sh Ping.bpel
> file:/opt/.../examples/PingPong/ping/BEA- generated.wsdl:0: error:
> [SchemaError] Error in schema processing: src-resolve.4.2: Error resolving
> component 'java:BEAExampleType'. It was detected that 'java:BEAExampleType'
> is in namespace 'java:com.thisprogram.beans ', but components from this
> namespace are not referenceable from schema document
> 'file:/opt/.../examples/PingPong/ping/BEA-generated.wsdl'. If this is the
> incorrect namespace, perhaps the prefix of 'java:BEAExampleType' needs to be
> changed. If this is the correct namespace, then an appropriate 'import' tag
> should be added to 'file:/opt/.../examples/PingPong/ping/BEA-
> generated.wsdl'.
> java org.apache.ode.tools.bpelc.cline.BpelC: error: [CompilationErrors]
> Compilation completed with 1 error(s).
> Thanks,
> Dan

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message