DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40896>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40896 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2006-11-05 08:55 ------- You Wss4j guy always using untested XMLSignature constructors!!! ;) Just joking. You hit again another XMLSignature constructor that there is no unit test for it. The problem is that for creating new Signatures(for signing) public XMLSignature( Document doc, String BaseURI, Element SignatureMethodElem, Element CanonicalizationMethodElem) throws XMLSecurityException Use the SignatureAlgorithm (Element) constructor, that normally is only used for verifying. The SignatureAlgorith obtain a java.security.Signature from the verifying pool but is going to be use for signing and when latter is recycled for verifying it gives you the error. Now the SignatureAlgorihtm is more lazy and only obtains a signature when asked for sign or verify and obtain it from the right pool. Anyway you are doing a lot of redundat work creating firs a SignatureAlgorithm DOMificated it and later make the XMLSignature library read it again from DOM. (Before the fix it will be worse as it obtain a new java.security.Signature that is even slower). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
