Hi, Yes it was the mismatch in the versions of the slf4j Logger which caused the crash.
I'll pay more attention to those messages next time. Cheers, Adrian -----Original Message----- From: Adrian Williamson [mailto:a...@octavo2.demon.co.uk] Sent: 14 August 2014 11:03 To: d...@ws.apache.org; users@ws.apache.org Subject: RE: Exception at org.apache.wss4j.dom.processor.SignatureProcessor.verifyXMLSignature(Signatu reProcessor.java:446) in Wss4J 2.0.2 Hi, I think it might have to do with these lines from the ouput: SLF4J: The requested version 1.6 by your slf4j binding is not compatible with [1.5.5, 1.5.6] SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details. As it seems to be failing in the Logging line: private static CacheManager findDefaultCacheManager(String confName, URL configFileURL) { try { Configuration conf = ConfigurationFactory.parseConfiguration(configFileURL); . . . public static Configuration parseConfiguration(final URL url) throws CacheException { LOG.debug("Configuring ehcache from URL: {}", url); I'll try and make that binding error go away. Adrian -----Original Message----- From: Adrian Williamson [mailto:a...@octavo2.demon.co.uk] Sent: 14 August 2014 09:22 To: d...@ws.apache.org Subject: Exception at org.apache.wss4j.dom.processor.SignatureProcessor.verifyXMLSignature(Signatu reProcessor.java:446) in Wss4J 2.0.2 Hi, I was hoping someone could shed some light on the cause of the exception attached in the text file "JavaStack.txt". I'm using the WSS4J API to decode a message with signed body and time stamp and encrypted body (using Certificates). It happens in the method decodeSOAP on the line: results = this.secEngine.processSecurityHeader(doc,null,this.callbackHandler,this.cryp to); I've dug down a little and I think it is trying to invoke a method that does not exist - but I don't have the skills to setup my Java installation so I can set a break point within the Reflection API. I've attached a good bit of the source, but it is in the decodeSOAP method - where I presume I have forgotten to initialise some aspect of the Wss4J interface Anyone know what I've not done? Thanks Adrian