On 11/5/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
Hi Raul,
On 11/5/06, Raul Benito <[EMAIL PROTECTED]> wrote:
> 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.
I just reviewed the WSS4J signature code ...the reason for using this
constructor is to provide the "CanonicalizationMethod" element
carrying an "InclusiveNamespaces" element, to be included in
"SignedInfo".
See here [1] for the code snippet from WSS4J where we create the
XMLSignature instance.
I will take a look, I promise. But this week will be impossible.
Anyway the fix in the svn head
