[
https://jira.jboss.org/browse/JBESB-3428?page=com.atlassian.jira.plugin.s...
]
Tom Fennelly commented on JBESB-3428:
-------------------------------------
I would imagine it is still an issue, unless Picketlink has been changed to use the same
version of the JAX-WS jars as WISE uses (I'd be fairly sure WISE has not changed).
This should be easy enough to test if you modify one of the WISE examples to include
security constraints on one of the services.
JAX-WS dependency mismatch between Picketlink/Security and WISE
components
---------------------------------------------------------------------------
Key: JBESB-3428
URL:
https://jira.jboss.org/browse/JBESB-3428
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Security, Web Services
Affects Versions: 4.9
Reporter: Tom Fennelly
Fix For: 4.9 CP1
JBoss AS5 + Java 6.
If you have an esb app that looks like a combo of the security_saml and one of the wise
examples.... you'll break. The saml code (Picketlink) requires the jboss-native
version of the jaxws jars from the server/client folder, while the wise code requires the
jaxws version from the ESB Server?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira