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 "Renaud Bruyeron (JIRA)" <ji...@apache.org> on 2007/05/21 11:48:16 UTC
[jira] Created: (WSS-75) remove dependency on xalan because it gets
in the way of trax resolution
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
[jira] Commented: (WSS-75) remove dependency on xalan because it
gets in the way of trax resolution
Posted by "verify@0spam.com (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (WSS-75) remove dependency on xalan because it
gets in the way of trax resolution
Posted by "verify@0spam.com (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (WSS-75) remove dependency on xalan because it
gets in the way of trax resolution
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved WSS-75.
------------------------------------
Resolution: Won't Fix
Marking this as "won't fix". There's no point in removing the xalan URI references from WSS4J, as they're needed at runtime anyway in xml-sec. So we can't remove the xalan dependency until xml-sec gets fixed accordingly.
> 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
[jira] Updated: (WSS-75) remove dependency on xalan because it gets
in the way of trax resolution
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated WSS-75:
--------------------------------
Assignee: (was: Davanum Srinivas)
> 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
>
> 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
[jira] Assigned: (WSS-75) remove dependency on xalan because it
gets in the way of trax resolution
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh reassigned WSS-75:
--------------------------------------
Assignee: Colm O hEigeartaigh
> 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
[jira] Closed: (WSS-75) remove dependency on xalan because it gets
in the way of trax resolution
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (WSS-75) remove dependency on xalan because it gets
in the way of trax resolution
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh updated WSS-75:
-----------------------------------
Comment: was deleted
> 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
>
> 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
[jira] Commented: (WSS-75) remove dependency on xalan because it
gets in the way of trax resolution
Posted by "Paul Harrison (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639052#action_12639052 ]
Paul Harrison commented on WSS-75:
----------------------------------
I agree that the dependency on xalan is very irritating when wanting to use other xsl processors - it seems to me looking at the code, that the only dependency is on the org.apache.xml.utils.URI class and this is only used in org.apache.ws.security.message.EnvelopeIdResolver - This might even be a longstanding error as a quick look at the code suggests that the standard java.net.URI could easily be used instead.
> 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
>
> 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
[jira] Updated: (WSS-75) remove dependency on xalan because it gets
in the way of trax resolution
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh updated WSS-75:
-----------------------------------
Affects Version/s: 1.5.4
Fix Version/s: 1.5.5
I think we can fix this given that support for JDK 1.3, which doesn't contain java.net.URI, has been dropped for 1.5.5
> 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
> 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
[jira] Commented: (WSS-75) remove dependency on xalan because it
gets in the way of trax resolution
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639901#action_12639901 ]
Colm O hEigeartaigh commented on WSS-75:
----------------------------------------
XML Security has a dependency on XALAN though, so is there any point in moving to java.net.URI in the WSS4J code?
> 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
>
> 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