ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "AilanChen (Commented) (JIRA)" <>
Subject [jira] [Commented] (WSS-301) WSS4J 1.6 incorrectly using XML-Security ResourceResolvers
Date Thu, 16 Feb 2012 01:59:01 GMT


AilanChen commented on WSS-301:

Thanks to "GoAgent" that i can over the GFW than konw this iusse.
Lived in China was very tangle!
> WSS4J 1.6 incorrectly using XML-Security ResourceResolvers
> ----------------------------------------------------------
>                 Key: WSS-301
>                 URL:
>             Project: WSS4J
>          Issue Type: Bug
>    Affects Versions: 1.6.1
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.6.2
>         Attachments: wss4j-1.6.2-SNAPSHOT.jar
> WSS4J 1.6.x is incorrectly using XML-Security ResourceResolvers to "resolve" DOM Elements
for use in signature creation and verification. WSS4J uses a custom IdResolver implementation
to call a custom ResourceResolverSpi instance. This IdResolver implementation uses "internal"* classes, and this is causing problems when using JDK 1.6 for signature creation
and validation in some containers (Jetty).
> WSS4J should be using the JSR-105 API instead to find and supply elements for signature/creation.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message