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.
Tue, 20 Oct 2009 20:59:31 -0700, /Jitendra Kotamraju/:
I am trying to resolve a JAX-WS bug
https://jax-ws.dev.java.net/issues/show_bug.cgi?id=777
In this case, I guess the user is running into a WSDL that has multiple
<xsd:schema> under <types>
for example:
<definitions ...>
<types>
<xsd:schema>
<xsd:import namespace="http://duke.example.org";
schemaLocation="add.xsd"/>
</xsd:schema>
<xsd:schema>
<xsd:import namespace="http://duke.example.org";
schemaLocation="add1.xsd"/>
</xsd:schema>
</types>
Here, JAX-WS impl passing the 4 DOMSources for the corresponding
<xsd:schema> nodes in WSDL+add.xsd+add1.xsd to
SchemaFactory.newSchema(). I thought this xerces feature would work for
this. But from your reply, the feature doesn't support this usecase.
Are there any plans to support such a usecase ?
Michael Glavassevich wrote:
"honour-all-schemaLocations" only applies today to multiple imports for the
same namespace contained directly or indirectly from a root schema
document. That doesn't seem to be how you're using it.
jitendra.kotamr...@sun.com wrote on 10/20/2009 08:19:03 PM:
I am trying to use the
"http://apache.org/xml/features/honour-all-schemaLocations"; feature
during schema validation and I couldn't get it work with xerces-2_9_1.
In this case, there are multiple schemas that are in the same
targetnamespace. I am attaching a simple testcase, can somebody point to
me if I am doing anything wrong here ?
--
Stanimir
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
