Hi Bill, One possibility is that the version of Xerces loaded in your test case may be different than the one loaded by Cocoon. Maybe Cocoon is using its own ClassLoader to load Xerces from some other location than your classpath. org.apache.xerces.parsers.StandardParserConfiguration was the default configuration in older versions such as Xerces 2.1.0. Are you using some version of JDK 1.4? That could be the source of the problem.
or... Perhaps Cocoon has changed the default parser configuration. The logic used by Xerces to select a parser configuration is described at http://xml.apache.org/xerces2-j/faq-xni.html#faq-2. The org.apache.xerces.xni.parser.XMLParserConfiguration system property takes precedence over other locations, so if you've set the property it should instantiate the configuration of your choice (provided that Cocoon doesn't change this value before it reads yours). Try setting this property to org.apache.xerces.parsers.XML11Configuration, and then check the actual configuration created for the DOMParser. Hope that helps. ----------------------------- Michael Glavassevich [EMAIL PROTECTED] 4B Computer Engineering University of Waterloo On Thu, 8 May 2003, Bill Raudabaugh wrote: > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
