Hi Peter,
I just found the same thing, trying to use BouncyCastle as the crypto
provider. Looks like somebody changed the constructor signature used by
the factory without changing any of the implementations except for Merlin.
- Dennis
Dennis M. Sosnoski
SOA, Web Services, and XML
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117
Peter Gerstbach wrote:
Hello,
has anybody succeeded using the IAIK crypto provider with WSS4J?
Just using the following line in crypto.properties produces an exception.
org.apache.ws.security.crypto.provider=iaik.security.provider.IAIK
java.lang.NoSuchMethodException:
iaik.security.provider.IAIK.<init>(java.util.Properties,
java.lang.ClassLoader)
at java.lang.Class.getConstructor0(Class.java:1937)
at java.lang.Class.getConstructor(Class.java:1027)
at
org.apache.ws.security.components.crypto.CryptoFactory.loadClass(CryptoFactory.java:141)
at
org.apache.ws.security.components.crypto.CryptoFactory.getInstance(CryptoFactory.java:115)
at
org.apache.ws.security.handler.WSHandler.loadSignatureCrypto(WSHandler.java:337)
at
org.apache.ws.security.handler.WSHandler.doSenderAction(WSHandler.java:123)
at
org.apache.ws.axis.security.WSDoAllSender.invoke(WSDoAllSender.java:170)
Is there a way to set the correct way to create the provider in the
properties file?
Regards,
Peter Gerstbach
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
