ozlevanon wrote:
This is a bit of a shot in the dark (I don't work with weblogic myself) but maybe trying to specify the xml reader yourself will fix that. You can try setting the system property "org.xml.sax.driver". Either by calling
System.setProperty("org.xml.sax.driver", "org.apache.crimson.parser.XMLReaderImpl")
Or by launching WebLogic with
-Dorg.xml.sax.driver=org.apache.crimson.parser.XMLReaderImpl
The value I used here (org.apache.crimson.parser.XMLReaderImpl) is one that solved similar problems for me in the past, I'm not sure it's the one you need...
Alternatively, it's possible that WebLogic loads its libraries before loading your application libraries, which might affect the behavior. There should be some option to configure it to load application libraries first, and only then WebLogic's libraries.
thank you for your reply!
I did set the system property by adding the -D property with various xml drivers, but when I do that, it still keeps throwing the same error message, except the change in the driver class name.