Rick, Thanks for your response. Both schemas are independent. The wrapper's schema allows for any XML content to be in its body. And the schema location of the body should be resolved when the first tag of that body is parsed. Is some resolver interface available that could be implemented and plugged in so every "xmlns" attribute gets a change to be resolved by custom code?
Cheers Jo On 1/29/07, Bullotta, Rick <[EMAIL PROTECTED]> wrote:
Jo - wouldn't the schema that defines the root type(s) import the child schema? If so, it should work fine without customization. - Rick *** Sent via BlackBerry -----Original Message----- From: Jo Vandermeeren <[EMAIL PROTECTED]> To: j-users@xerces.apache.org <j-users@xerces.apache.org> Sent: Mon Jan 29 01:21:29 2007 Subject: Resolving multiple XSDs/namespaces Hi fellow xerces users, The project I'm working on uses XML as transport wrapper for data, much like a SOAP wrapper that contains XML content. I want to parse and validate the entire message in 1 run, and need to use 2 XSD schemas. The XSD's used for validation are packaged inside our application and need to be resolved locally.. I can attach an EntityResolver on the parser, but only one call is issued to resolve the first encountered schemaLocation or noNamespaceSchemaLocation. It doesn't prompt me for the second one. Any ideas? Is a resolver available to resolve each encountered xmlns/schemaLocation attribute? Here's a little example of how the message structure looks like: <root xmlns="http://www.example.com/root";> <inrootnamespace/> <child xmlns="http://www.example.com/child";> <inchildnamespace/> </child> </root> Cheers Jo
