You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Dan <le...@gmail.com> on 2007/07/05 17:01:36 UTC
WSDL import error on wsdl generated by weblogic workbench
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
Re: WSDL import error on wsdl generated by weblogic workbench
Posted by Dan <le...@gmail.com>.
Hi,
I ran some more experiments this morning. I can't import the wsdl in
PingPong or HelloWorld2 if I use the 2001 uri. I changed all the xml schema
uri's to 2001 and still had no luck, so it seems to not be a problem of
multiple xml schema namespaces mixed in the same project. There must be
something about the format of that wsdl file that WSDL4J or some other
library doesn't feel is kosher with 2001. Note that 2001 works fine for the
other wsdl files (Ping, Pong, HelloWorld2).
Thanks,
--Dan
On 7/9/07, Paul Brown <pa...@gmail.com> wrote:
>
> Hi, Dan --
>
> > The additional import line in the schema section turned out not to be
> > necessary. What I did find was make or break was the xml schema
> namespace
> > itself.
> > Changing from...
> > xmlns:xs="http://www.w3.org/2001/XMLSchema"
> > to
> > xmlns:xs="http://www.w3.org/2000/10/XMLSchema"
> > ...seems to have resolved the import problem.
>
> Gah. The 2001 URI is the right one from a basic profile perspective
> and other perspectives as well.
>
> I grep'd through the codebase, and the 2000 URI appears in some sample
> files (JBI pingpong, for example) but not in any of the Java files.
> (I checked the intersection of the set of files that contain "Schema"
> and "2000".)
>
> > I'm not sure if its a case of using multiple xml schema namespaces in
> the
> > same bpel project or if 2001 will always fail.
>
> I'm surprised that the 2000 URI worked... I suspect that the culprit is
> WSDL4J:
>
> http://tinyurl.com/yvphxg
>
> I'd try going with all 2001 schemas if you can.
>
> --
> paulrbrown@gmail.com
> http://mult.ifario.us/
>
Re: WSDL import error on wsdl generated by weblogic workbench
Posted by Paul Brown <pa...@gmail.com>.
Hi, Dan --
> The additional import line in the schema section turned out not to be
> necessary. What I did find was make or break was the xml schema namespace
> itself.
> Changing from...
> xmlns:xs="http://www.w3.org/2001/XMLSchema"
> to
> xmlns:xs="http://www.w3.org/2000/10/XMLSchema"
> ...seems to have resolved the import problem.
Gah. The 2001 URI is the right one from a basic profile perspective
and other perspectives as well.
I grep'd through the codebase, and the 2000 URI appears in some sample
files (JBI pingpong, for example) but not in any of the Java files.
(I checked the intersection of the set of files that contain "Schema"
and "2000".)
> I'm not sure if its a case of using multiple xml schema namespaces in the
> same bpel project or if 2001 will always fail.
I'm surprised that the 2000 URI worked... I suspect that the culprit is WSDL4J:
http://tinyurl.com/yvphxg
I'd try going with all 2001 schemas if you can.
--
paulrbrown@gmail.com
http://mult.ifario.us/
Re: WSDL import error on wsdl generated by weblogic workbench
Posted by Dan <le...@gmail.com>.
Hi Alex,
Thanks for posting the build.
The additional import line in the schema section turned out not to be
necessary. What I did find was make or break was the xml schema namespace
itself.
Changing from...
xmlns:xs="http://www.w3.org/2001/XMLSchema"
to
xmlns:xs="http://www.w3.org/2000/10/XMLSchema"
...seems to have resolved the import problem.
I'm not sure if its a case of using multiple xml schema namespaces in the
same bpel project or if 2001 will always fail.
Thanks,
Dan
On 7/5/07, Alex Boisvert <bo...@intalio.com> wrote:
>
> BTW, I just fixed an issue in trunk related to xsd:import without
> schemaLocation. So you'll want to use r553662 or later to make your WSDL
> work.
>
> alex
>
>
> On 7/5/07, Alex Boisvert <bo...@intalio.com> wrote:
> >
> > Hi Dan,
> >
> > The first schema definition requires a <xsd:import> to reference types
> > from a different namespace.
> >
> > e.g.
> > <xs:schema attributeFormDefault="unqualified"
> > elementFormDefault="qualified"
> > targetNamespace="http://example.org"
> > xmlns:xs="http://www.w3.org/2001/XMLSchema ">
> >
> > <xs:import namespace="java:com.thisprogram.beans"/>
> >
> > ...
> > ...
> > </xs:schema>
> >
> > alex
> >
> > On 7/5/07, Dan <le...@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
> > >
> > >
> >
>
Re: WSDL import error on wsdl generated by weblogic workbench
Posted by Alex Boisvert <bo...@intalio.com>.
BTW, I just fixed an issue in trunk related to xsd:import without
schemaLocation. So you'll want to use r553662 or later to make your WSDL
work.
alex
On 7/5/07, Alex Boisvert <bo...@intalio.com> wrote:
>
> Hi Dan,
>
> The first schema definition requires a <xsd:import> to reference types
> from a different namespace.
>
> e.g.
> <xs:schema attributeFormDefault="unqualified"
> elementFormDefault="qualified"
> targetNamespace="http://example.org"
> xmlns:xs="http://www.w3.org/2001/XMLSchema ">
>
> <xs:import namespace="java:com.thisprogram.beans"/>
>
> ...
> ...
> </xs:schema>
>
> alex
>
> On 7/5/07, Dan <le...@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
> >
> >
>
Re: WSDL import error on wsdl generated by weblogic workbench
Posted by Alex Boisvert <bo...@intalio.com>.
Hi Dan,
The first schema definition requires a <xsd:import> to reference types from
a different namespace.
e.g.
<xs:schema attributeFormDefault="unqualified"
elementFormDefault="qualified"
targetNamespace="http://example.org"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="java:com.thisprogram.beans"/>
...
...
</xs:schema>
alex
On 7/5/07, Dan <le...@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
>
>