You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2008/12/22 15:04:46 UTC
[jira] Closed: (WSS-75) remove dependency on xalan because it gets
in the way of trax resolution
[ https://issues.apache.org/jira/browse/WSS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh closed WSS-75.
----------------------------------
> remove dependency on xalan because it gets in the way of trax resolution
> ------------------------------------------------------------------------
>
> Key: WSS-75
> URL: https://issues.apache.org/jira/browse/WSS-75
> Project: WSS4J
> Issue Type: Wish
> Affects Versions: 1.5.4
> Reporter: Renaud Bruyeron
> Assignee: Colm O hEigeartaigh
> Fix For: 1.5.5
>
>
> Here's the use-case:
> * We are in one of several webapps in a tomcat 5.5.20 instance
> * WSS4J is used for WS security: xalan.jar is required in the classpath
> * saxon must be the trax transformer because we use XSLT 2.0
> It is not simple to have saxon and xalan cohabit in the same classloader in a webapp: using -Djavax.xml.transform.TransformerFactory has a JVM-wide impact (other webapps may want to use xalan as their trax processor...) and therefore it may not always be possible/allowed.
> How much work would it be to *not* depend explicitly on xalan.jar and use standard APIs instead?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org