EbMS with custom xsd document which import other xsd's

Question

Hi,
I've created a ebMS partner agreement with a custom document type, which is actually importing other xsd's.
When trying to create the AQ Adapter service WSDL, it returns a WSDL Read Error, with an error importing schema's. Unable to parse schema ...
It looks like the imported xsd's are not deployed.
Anyone seen this before ?
Thanks,
Guido

Answer 1

It is definitely possible to use XSDs that reference other XSDs in Oracle B2B 10g for "Custom Document over ebMS".
Whether or not it matters whether you use "import" or "include" I'm not sure, but import works as long as your schemas validate end-to-end with namespaces and such.
You need to ensure that all the paths in your schemas are relative rather than pointing to files on your hard drive's filesystem or on the Internet.
So you'll have something like this in your root schema:
<xsd:import schemaLocation="foo.xsd" namespace="http://example.com/foo">
<xsd:import schemaLocation="bar.xsd" namespace="http://example.com/bar">
When you create a ZIP file containing all the schemas required, make sure everything is top-level in the ZIP file (i.e., no subdirectories at all). Then you upload the ZIP file and in the next box tell B2B the name of the root schema. For the example above, you'd have a ZIP file containing:
root.xsd
foo.xsd
bar.xsd
Of course you can have subdirectories and stuff in the ZIP file, but then you'll need to specify relative paths in your root XSD that reflect that.
Also, if the schemas you are importing in turn import other schemas, you need to alter them to use relative paths and include them in your ZIP file.
Hope this helps!