Hi Werner,
I am a little curious to know why Axis2 explicitly listed BouncyCastle as a requirement even on Java 1.5. dims was kind enough to point me towards http://mail-archives.apache.org/mod_mbox/ws-fx-dev/200403.mbox/[EMAIL PROTECTED] Since that message is a bit old and since several additions have been made to JCE support on Java 1.5, perhaps you could give us an update on what crypto features required by wss4j are still missing? Also, are there any issues apart from minor inconsistencies in algorithm/mode/padding transformations etc. which make the Axis2/wss4j codebase dependent on Bouncycastle? For related discussion on axis2-dev please see the thread at: http://marc.theaimsgroup.com/?l=axis-dev&m=115221023017200&w=2
Thanks in advance!
Vivek



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to