Stanimir Stamenkov <s7a...@netscape.net> wrote on 10/24/2009 11:12:16 AM:
> Wed, 21 Oct 2009 14:34:25 -0700, /Jitendra Kotamraju/: > > Stanimir Stamenkov wrote: > > > >> I guess one could prepare a source schema which contains only > >> <xsd:import>s of the given <xsd:schema> elements. The <xsd:import> > >> locations could use custom URIs like "urn:x-jax-ws-import-a", > >> "urn:x-jax-ws-import-b" which would be resolved by a custom resource > >> resolver. I think the "honour-all-schemaLocations" feature should > >> work this way. > > > > Yes, I was thinking the same to create a pseudo schema comprising of all > > the schema fragements <types>/<xsd:schema> in the wsdl(but it is bit of > > a work, since those imports also need to have correct namespace etc). > > The <xsd:import>s need to have 'namespace' attribute with value of > the 'targetNamespace' of the corresponding <xsd:schema> element, but > that's not awful lot of work, IMO. If you're synthesizing schema documents to glue together the ones in the WSDL then you may not even need to use "honour-all-schemaLocations". Create a schema document for each namespace with <xs:include>s (for each schema document in the WSDL with that target namespace) and then combine those together with <xs:import>s for each of those namespaces in a "master" schema document. That should work with any schema processor, not just those which honour multiple imports for the same namespace. > -- > Stanimir > > --------------------------------------------------------------------- > To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org > For additional commands, e-mail: j-users-h...@xerces.apache.org Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org
