XSD import fails

[radomir.kadlec]

Hello,

I use imported XSD which contains another importet XSD in the cxfbc-consumer.

I thing, the definitions are correct.

But there is a WARNING in the log and the message validations for this endpoint take no effect.

The ServiceMix treat the schema as invalid and uses it not.

I can see in the log, that the both XSD files are merged to one from apache.xercs.

But the from xerces merged schema seems not to be correct, because it uses a prefix gin with namespace, to that is no schema definition available.

The wsdl definition of the endpoint contains only import of the document.xsd, but the elements from this xsd are not used, because the message content is represented with xs:any element. ServiceMix uses than the schema for the message validation, if the schema is correct (but it is not so).

What is wrong? The schema definition? The xerces implementation? Or FuseESB configuration?

The log with the error message and with the merged schema see result.log.

The imported schema see gin_to_import.xsd.

The document schema see document.xsd.

Part of the wsdl see wsdl_part.wsdl.

Thanks

Radomir Kadlec

Edited by: kadlec on May 25, 2012 7:58 AM

Edited by: kadlec on May 25, 2012 8:29 AM

Edited by: kadlec on May 25, 2012 8:30 AM

[davsclaus]

What version of Fuse ESB are you using? And did it work before etc?

If you have a FuseSource subscription I suggest to use that channel to ask for help.

[radomir.kadlec]

Hello,

I use the FuseESB apache-servicemix-4.4.1-fuse-02-05 and have no FuseSource subscriptions.

I did not use xsd imports in previous versions of FuseESB, so I can not give you any reports to the behaviour in prevous versions.

I cannot use the newest apache-servicemix-4.4.1-fuse-03-06 because of Java crash with this newest version on 64 bit AMD machine.

(To this Java error you can see my post on http://servicemix.396122.n5.nabble.com/ServiceMix-4-4-1-fuse-03-06-Java-machine-crashing-on-64-bit-server-during-startup-tp5669931.html)

Thank you,

Radomir