You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "verify@0spam.com (JIRA)" <ji...@apache.org> on 2007/05/23 17:41:16 UTC

[jira] Commented: (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:comment-tabpanel#action_12498271 ] 

verify@0spam.com commented on WSS-75:
-------------------------------------

ATTENTION!

A message you recently sent to a 0Spam.com user with the subject "[jira] Created: (WSS-75) remove dependency on xala..." was not delivered because they are using the 0Spam.com anti-spam service.  Please click the link below to confirm that this is not spam. When you confirm, this message and all future messages you send will automatically be accepted.

http://www.0spam.com/v.cgi?user=1086966126&verify=692618


========================================
This is an automated message from 0Spam.com.
Please do not reply to this Email.

Looking for a free anti-spam service?
Visit us at http://www.0spam.com to find out more.


> 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
>            Reporter: Renaud Bruyeron
>         Assigned To: Davanum Srinivas
>
> 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