Ok, the plot thickens. While my test case works with the classpath changed, my application exhibits the original problem regardless of how much path twiddling I do. My application is running in Cocoon while my test case runs standalone. I do suspect that there may be something in the Cocoon classes that are affecting this.
I've found in my test case that when it is working parser.DOMParser.fConfiguration is pointing at org.apache.xerces.parsers.XML11Configuration. This is good since this is expecting XML Schema validation. But when it is not working, for some reason parser.DOMParser.fConfiguration is point at org.apache.xerces.parsers.StandardParserConfiguration. Why would the same code produce two different configurations? How can I ensure that the XML11Configuration is always used? -----Original Message----- From: Bill Raudabaugh [mailto:[EMAIL PROTECTED] Sent: Thursday, May 08, 2003 3:49 PM To: [EMAIL PROTECTED] Subject: RE: Accessing PSVI through DOM Good grief! It was a classpath problem .... [snip] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
