-
1. Re: problem with loader-repository and JAR in web-inf/lib
starksm64 Feb 20, 2006 6:56 PM (in response to srouil)You cannot overload the jdk javax.* classes from the war deployment. Only the associated implementation classes should be in the jar. Remove the javax.* classes from the jar or configure the war class loader to ignore these using the jbossweb-tomcat55.sar/META-INF/jboss-service.xml FilteredPackages setting.
-
2. Re: problem with loader-repository and JAR in web-inf/lib
srouil Feb 21, 2006 3:12 AM (in response to srouil)From what I have tried, I see that the javax.xml classes are loaded from the JDK or JBoss anyway, no matter what I set in FilteredPackages
How should I process to create an Oracle SAX parser with the following code if this code is in a class that is deployed in WARs web-inf/lib ?
SAXParserFactory factory = SAXParserFactory.newInstance();
SAXParser parser = factory.newSAXParser();
As reminder, the Oracle XML parser is in the EAR and its JAR is added to WAR's manifest classpath -
3. Re: problem with loader-repository and JAR in web-inf/lib
dalingxu Sep 25, 2006 8:55 PM (in response to srouil)I am facing exactly the same issue like you did.
Did you solve it? How did you do it?
Thanks"srouil" wrote:
From what I have tried, I see that the javax.xml classes are loaded from the JDK or JBoss anyway, no matter what I set in FilteredPackages
How should I process to create an Oracle SAX parser with the following code if this code is in a class that is deployed in WARs web-inf/lib ?
SAXParserFactory factory = SAXParserFactory.newInstance();
SAXParser parser = factory.newSAXParser();
As reminder, the Oracle XML parser is in the EAR and its JAR is added to WAR's manifest classpath