Vito Caleandro [EMAIL PROTECTED] wrote on 12/05/2006
09:30:55 AM:
Hi all,
in a SOAP-message validation I set the parser feature
honour-all-schemaLocations of Xerces parser as follows:
...
xmlvalidate failonerror=no warn=yes
classname=org.apache.xerces.parsers.SAXParser
Our XML file starts with :
ourproj:rootXmlTag xmlns:ourproj=http://www.ourwebsite.com/ourproj;
The XML schema corresponding to http://www.ourwebsite.com/ourproj is to be
generated by our code from database.
This is done by our own EntityResolver interface implementation.
When we try to
this problem seems to occur only when i use JDK1.4.
i have the following system properties set, which i thought would make this
go away, but unfortunately not...
System.setProperty(org.xml.sax.driver,
org.apache.xerces.parsers.SAXParser);
I am always using the endorsed arguments -Djava.endorsed.dirs to be
sure I get the right xerces.
Maybe this helps,
DicK Deneer
Op 5-dec-2006, om 23:49 heeft ptomsic het volgende geschreven:
this problem seems to occur only when i use JDK1.4.
i have the following system properties set,
You're probably picking up an incompatible mix of classes from Xerces
2.8.1 and some old version of Xerces (something prior to 2.7.0) which is
somewhere on your classpath or perhaps in the endorsed directory of your
JDK 1.4 installation.
Michael Glavassevich
XML Parser Development
IBM Toronto
Our XML file looks something like :
ourproj:rootXmlTag xmlns:ourproj=http://www.ourwebsite.com/ourproj;
...
The XML schema corresponding to http://www.ourwebsite.com/ourproj is to be
generated by our code from database.
This is done by our own EntityResolver implementation.
When we try to
