Does your application have a JAXP parser bundled? There is some behavior
change in how the JAXP parser is picked up since b43. Before b43, the
system default JAXP parser is always picked up (which is the one came
with JDK1.5) to parse the deployment descriptors. After b43, if there is
a parser packaged in the user application, that parser will be given
higher priority which is the expected behavior specified in
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/parsers/SAXParserFactory.html#newInstance
glassfish_at_javadesktop.org wrote:
>Hi, John.
>
>The DeploymentDescriptorFile class that invokes the parser as identified in the stack trace has not changed since January (build 34), so at least that class has been stable between the earlier build when your app deployed and now Not that it's the only possible class in which a change might be causing the difference in behavior you've reported, but at least it's nothing obvious like that.
>
>Do you still have build 41 installed? If so, have you confirmed that deploying exactly the same WAR that fails now with the later build still works now with the earlier one?
>
>Which JDK were you using earlier? Which one now?
>
>- Tim
>- Tim
>[Message sent by forum member 'tjquinn' (tjquinn)]
>
>http://forums.java.net/jive/thread.jspa?messageID=224752
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>