Hi,
This could be a problem in our side because we call the XMLBeans
compiler programmatically with a bunch of Axis2 specific
configurations and we may be missing a certain option. We appreciate
if you can create a jira and attach the WSDL
thanks
Ajith
On 6/18/07, Desmond Whewell (CV/ETL) <[EMAIL PROTECTED]> wrote:
Using: Axis2 1.2, xmlbeans 2.2.0
I have a wdsl file and a set of schemas that I am trying to process
using wsdl2java. When invoked, wsdl2java fails with:
-------
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerati
onEngine.java:256)
...
... Stuff chopped out
...
Caused by: org.apache.xmlbeans.XmlException:
project://local/<my>.xsd:3:1: error: Included schema has a target
namespace "one-uri" that does not match the source namespace "two-uri"
at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaT
ypeSystemCompiler.java:225)
-------
Note: the above is obfuscated, but it shows the intent.
The wsdl file and schema set are valid, according to XMLSpy.
As an experiment, I downloaded xmlbeans 2.2.0 and compiled the very same
wsdl file. xmlbeans completed without complaint, generating all of the
expected class and xsb files.
In short, why does Axis2 and xmlbeans have different behaviour when
processing identical schemas.
I can always fall back to calling Axis2 with no data binding and then
use the explicit xmlbeans classes, but I'd prefer to use the monolithic
approach.
Cheers, Des
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
