Hi Jitu,
There are no plans to make "honour-all-schemaLocations" do more than it
currently does.
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrgla...@ca.ibm.com
E-mail: mrgla...@apache.org
jitendra.kotamr...@sun.com wrote on 10/20/2009 11:59:31 PM:
> Michael,
>
Michael,
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
under
for example:
http://duke.example.org";
schemaLocation="add.xsd"/>
Hi Jitu,
"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.
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrgla...@ca.i
Hi Brenda,
The element names in your document must match the elements declared in your
schema. Their namespace is part of the name. The default namespace is
terminology for the namespace binding for elements (and QNames in content)
with no prefix. Also, the prefixes you declare in the schema have
Ok - I have made progess!! Based on a post I saw in the forums, I switched
the way I set the schemas and that has improved things tremendously. I am no
longer getting that wacky error about OpenDNS. However, the parser is still
not validating my XML file as I would expect it to.
Here is the XML
One more thing - I am attaching the two "external" schemas - xmime and
xop-include.
Brenda Coulson wrote:
>
> Michael
>
> Thank you for your reply. Unfortunately there is no "OpenDNS" showing up
> anywhere in my XML or source code files. It is quite bizarre. The fact
> that I can get the XML to
Michael
Thank you for your reply. Unfortunately there is no "OpenDNS" showing up
anywhere in my XML or source code files. It is quite bizarre. The fact that
I can get the XML to validate with the XMLValidator from Spring tells me
that the XML is valid and that I can use the remote locations of xm
Hi Felix,
It probably doesn't matter but you may want to check with the Xalan folks.
Xerces-J 2.9.0 and Xalan 2.7.1 were meant to be released within days of
each other. The jar was supposed to have the same contents in both, though
even with the delay of their release I don't recall that they mad
Hi,
I downloaded xerces-2.9.0. Under docs/install.html mentions:
Serializer.jar : Jar file containing the Apache Xalan serializer. Currently the
serializer included in Xalan 2.7.1 is distributed with Xerces-J.
However, the md5 sums of serializer.jar in xerces-2.9.0 and xalan-2.7.1 differ!:
f0f
Hi Brenda,
The error message you're getting complains about "OpenDNS" appearing in
some document yet doesn't appear in any of the data you've shown. Such text
doesn't just appear magically. There's some other document involved here
that you haven't posted. It would help if you could make a connec
Hi Mark,
Mark Brucks wrote on 10/19/2009 08:20:27 PM:
> I'm having trouble understanding how information about derived types
> is maintained. I have a schema with a derived type declared, and an
> instance document which uses it (via xsi:type). I know that this type
> information is maintained
11 matches
Mail list logo
