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=40290>. 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=40290 Summary: NPE SignedInfo.getCanonicalizationMethodURI 1.4.Beta2 Product: Security Version: cvs Platform: Other OS/Version: Linux Status: NEW Severity: regression Priority: P2 Component: Canonicalization AssignedTo: security-dev@xml.apache.org ReportedBy: [EMAIL PROTECTED] When I'm using xmlsec 1.3.0 my WSS4J code is correctly generating a WS-Security signature. But, when I change the runtime to use xmlsec 1.4.Beta2, then I get the following NPE. I've build xmlsec 1.4.Beta2 from the latest svn tree. So for the moment JSR105 and WS-Security do not go along very well. Regards, Frank. Caused by: java.lang.NullPointerException at org.apache.xml.security.signature.SignedInfo.getCanonicalizationMethodURI(SignedInfo.java:301) at org.apache.xml.security.signature.SignedInfo.signInOctectStream(SignedInfo.java:275) at org.apache.xml.security.signature.XMLSignature.sign(XMLSignature.java:499) at org.apache.ws.security.message.WSSecSignature.computeSignature(WSSecSignature.java:599) -- 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.
