[ 
https://issues.apache.org/jira/browse/WSS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259778#comment-15259778
 ] 

Colm O hEigeartaigh commented on WSS-576:
-----------------------------------------

No SECURITY_ERROR does not exist in XML Sec, only in WSS4J. However, if 
WSSec.init() is called before XMLSec is initialised, then the WSS4J resource 
bundle is used for WSS4J. If not then the XML Sec resource bundle is used. Do 
you have a test-case or demo I could run to reproduce the issue?

> No message with ID "SECURITY_ERROR" found in resource bundle
> ------------------------------------------------------------
>
>                 Key: WSS-576
>                 URL: https://issues.apache.org/jira/browse/WSS-576
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Core
>    Affects Versions: 2.0.7
>         Environment: Any
>            Reporter: Namrata Jaiswal
>            Assignee: Colm O hEigeartaigh
>            Priority: Critical
>             Fix For: 2.0.8
>
>         Attachments: graycol.gif, graycol.gif, graycol.gif, graycol.gif
>
>
> When decryption fails Stax API throws unfriendly exception,
> Caused by: javax.xml.stream.XMLStreamException: 
> org.apache.wss4j.common.ext.WSSecurityException: No message with ID 
> "SECURITY_ERROR" found in resource bundle 
> "org/apache/xml/security/resource/xmlsecurity"
>       at 
> org.apache.wss4j.stax.impl.WSSecurityStreamReader.next(WSSecurityStreamReader.java:56)
>       at javax.xml.stream.util.StreamReaderDelegate.next(Unknown Source)
>       at 
> org.apache.axiom.om.impl.builder.SafeXMLStreamReader.next(SafeXMLStreamReader.java:185)
>       at 
> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:639)
>       at 
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:187)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to