[
https://issues.jboss.org/browse/WFCORE-2805?page=com.atlassian.jira.plugi...
]
David Lloyd commented on WFCORE-2805:
-------------------------------------
I think this will suffer from the same problems as all the other JAXP module replacement
ideas, namely that class loading is done poorly and/or static and global or per-TCCL
provider replacement is not possible or does not function correctly.
The following JBoss-maintained APIs and their implementations are not replaceable for the
same reason:
* {{javax.xml.datatype.DatatypeFactory}}
* {{javax.xml.parsers.DocumentBuilderFactory}}
* {{javax.xml.parsers.SAXParserFactory}}
* {{javax.xml.validation.SchemaFactory}}
* {{javax.xml.transform.sax.SAXTransformerFactory}}
* {{javax.xml.stream.XMLEventFactory}}
* {{javax.xml.stream.XMLInputFactory}}
* {{javax.xml.stream.XMLOutputFactory}}
* {{org.xml.sax.XMLReader}}
* {{javax.xml.xpath.XPathFactory}}
Java 9 *may* solve enough of the class loading problems that we use the JDK APIs, if not
the implementations.
Use Xalan from JRE rather than our own fork
-------------------------------------------
Key: WFCORE-2805
URL:
https://issues.jboss.org/browse/WFCORE-2805
Project: WildFly Core
Issue Type: Task
Reporter: Peter Palaga
Assignee: Peter Palaga
As proposed by [~wolfc] we want to check if we can get rid of maintaining our own fork of
Xalan.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)