It looks like you aren't calling WSSConfig.init() to initialise WSS4J. Are
you instead calling the XML Security Init.init() somewhere?
Colm.
On Mon, Jul 27, 2015 at 5:26 PM, stephen.ctr.chapp...@faa.gov wrote:
When processing a message with a malformed timestamp, I’m getting the
following
@cxf.apache.org
Subject: Re: Weird WSSecurityException details in WSS4J 2.1
It looks like you aren't calling WSSConfig.init() to initialise WSS4J. Are you
instead calling the XML Security Init.init() somewhere?
Colm.
On Mon, Jul 27, 2015 at 5:26 PM, stephen.ctr.chapp...@faa.gov wrote:
When processing
When processing a message with a malformed timestamp, I'm getting the following
detail text back in my WSSecurityException:
org.apache.wss4j.common.ext.WSSecurityException: No message with ID
invalidTimestamp found in resource bundle
org/apache/xml/security/resource/xmlsecurity
Am I missing a
