[
https://issues.apache.org/jira/browse/AMQ-9005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811545#comment-17811545
]
Joe Kesselman commented on AMQ-9005:
------------------------------------
Note that the JAXP/javax implementation shipped with most (all?) JREs *is* a
shadowed version of Xalan, though JAXP can be configured to select other
processors -- including current Xalan releases. I agree that at this point you
should probably be calling the JAXP factories rather than Xalan's older
"native" API (unless you need a feature that JAXP doesn't expose), but for an
Apache project I would still suggest configuring that for Apache Xalan. "We're
not dead yet!"
> 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: 2h 20m
> 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)
