- Should we set these system properties to use our JAXP implementations? 2) set these system properties at startup like so:
Why is the class used from the __redirected package for the JAXP factory implementations?
Using a different Streaming XML API provider in EAP 6
Our application in EAP 5 to use the old bea streaming API and we used to set the properties below, but with JBoss EAP 6 there is a clash causing my Web / SOAP application to stop working. What is the best way to continue to use our previous streaming provider and may it Available to my application ?
-Djavax.xml.stream.XMLOutputFactory=com.bea.xml.stream.XMLOutputFactoryBase -Djavax.xml.stream.XMLInputFactory=com.bea.xml.stream.MXParserFactory -Djavax.xml.stream.XMLEventFactory=com.bea.xml.stream.EventFactory
- We were wondering if it is safe to change XML transformers or not? One of our developers wants to swap in a new XML library and we want to verify it is JBoss-safe or not. The library is
Saxon-HE-22.214.171.124.jarand it will be deployed as a global module, and enabled via a startup parameter equivalent to the below code, is there any concerns in doing this way from JBoss side?
- Is it safe to change XML transformers by setting system properties ?
- Red Hat JBoss Enterprise Application Platform (EAP)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.