You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Alexandre Vermeerbergen (Jira)" <ji...@apache.org> on 2020/12/08 10:16:00 UTC

[jira] [Commented] (TOMEE-2938) [TCK/Certification] Xalan missing for JSTL xml:transform

    [ https://issues.apache.org/jira/browse/TOMEE-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17245795#comment-17245795 ] 

Alexandre Vermeerbergen commented on TOMEE-2938:
------------------------------------------------

Please don't re-introduce Xalan, removed through https://issues.apache.org/jira/browse/TOMEE-2743, because Xalan is poorly maintained.

For example, we had blocking issue with 'Invalid XML generated by XLST on characters from Unicode Supplementary Planes', tracked by https://issues.apache.org/jira/browse/XALANJ-2419 for which PR is still not integrated 2 years after being submitted.

I believe that Apache TomEE community should rather leverage JAX Transform existing API & implementation to get TCK tests working, rather than re-introducing obsolete dependencies such as Xalan.


That's my 2 cents :)

Kind regards,
Alexandre Vermeerbergen

> [TCK/Certification] Xalan missing for JSTL xml:transform
> --------------------------------------------------------
>
>                 Key: TOMEE-2938
>                 URL: https://issues.apache.org/jira/browse/TOMEE-2938
>             Project: TomEE
>          Issue Type: Bug
>            Reporter: Jean-Louis Monteiro
>            Priority: Major
>             Fix For: 8.0.6
>
>
> TomEE does not embed Xalan as XSLT Transformer at the moment.
> But Jakarta EE offers JSTL xml:transform why requires an XSLT Processor.
>  
> We need to add it back in the box.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)