[
https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=796913&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796913
]
ASF GitHub Bot logged work on AMQ-9005:
---------------------------------------
Author: ASF GitHub Bot
Created on: 01/Aug/22 14:27
Start Date: 01/Aug/22 14:27
Worklog Time Spent: 10m
Work Description: pjfanning commented on PR #870:
URL: https://github.com/apache/activemq/pull/870#issuecomment-1201279751
> xalan reference missed:
>
>
https://github.com/apache/activemq/blob/main/assembly/src/release/examples/conf/resin-web.xml
I'm guessing but that TransformerFactory setting can probably just be
removed. That would likely mean that the JDK built-in transformer is used
(unless another JAXP compliant transformer was on the classpath, eg Saxon).
Issue Time Tracking
-------------------
Worklog Id: (was: 796913)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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)
