[ https://issues.apache.org/jira/browse/AMQ-9005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573789#comment-17573789 ]
Matt Pavlovich edited comment on AMQ-9005 at 8/1/22 2:28 PM: ------------------------------------------------------------- [~tetlucas] more references here: https://github.com/apache/activemq/blob/main/assembly/src/release/examples/conf/resin-web.xml Other xalan references need to be cleaned up and XPath unit tests validated ./activemq-client/src/main/java/org/apache/activemq/filter/XPathExpression.java ./activemq-broker/src/main/java/org/apache/activemq/filter/XalanXPathEvaluator.java was (Author: mattrpav): [~tetlucas] one more reference here: https://github.com/apache/activemq/blob/main/assembly/src/release/examples/conf/resin-web.xml > remove xalan dependency due to it being end of life > --------------------------------------------------- > > Key: AMQ-9005 > URL: https://issues.apache.org/jira/browse/AMQ-9005 > Project: ActiveMQ > Issue Type: Improvement > Reporter: PJ Fanning > Assignee: Jean-Baptiste Onofré > Priority: Major > Fix For: 5.18.0, 5.17.2 > > Time Spent: 50m > Remaining Estimate: 0h > > Xalan is no longer supported. > https://lists.apache.org/thread/s8kjny5270ssfcp46v0fl39lk98987w7 > It is better to use JAXP TransformerFactory than using xalan directly. If you > add xalan dependency just to ensure that you have a JAXP compliant > transformer on the classpath, this is unnecessary - the Java runtime has a > built-in implementation. -- This message was sent by Atlassian Jira (v8.20.10#820010)