NEP Strange Behavior in Choosing XML Parsers
(Doc ID 1964392.1)
Last updated on JANUARY 25, 2019
Applies to:Oracle Communications ASAP - Version 7.2.0 and later
Information in this document applies to any platform.
For some reason, in $ASAP_HOME/JLIB directory, there are 3 different XML parser implementations - crimson.jar, xerces.jar, xmlparserv2.jar. Even though crimson.jar and xerces.jar don't appear in Java classpath, somehow they are present when JInterpreter executes customer Java code in ASAP cartridges. This is strange and leads to undesirable side effects - e.g. when we use JAXB marshalling, we get an error in JNEP log file "Exception: Security features for the SAX parser could not be enabled."
To work around this, we updated xerces.jar in JLIB directory to the latest 2.11 version and the error went away. However, in another environment, the error persists even after we update xerces.jar. The temporary workaround that we found is to remove crimson.jar from JLIB.
However, now we start seeing "WARNING: Using XDK. No security features will be enabled for the SAX parser." in ASAP.console file (which means somehow Oracle XDK is used instead of Apache Xerces):
Jan 15, 2015 11:58:12 AM com.sun.jersey.core.impl.provider.xml.SecureSAXParserFactory
WARNING: Using XDK. No security features will be enabled for the SAX parser.
This behavior is confusing. How can we configure ASAP to use xerces.jar for Java cartridge code.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document