Hi all,
Since using Chinese in soap messages which had their header encrypt was not
working (and after visiting the XML security page) I upgraded the libraries to
1.4.1 as recommended.
And now I have the following exception on the serverside:
com.ctc.wstx.exc.WstxParsingException: Undeclared nam
> Is this the way things ought to be, or should the canonicalization be
> checking the namespace and prefix components on each element, and
including
> an xmlns attribute when any change occurs between an element and its
parent?
I'm not certain, but I don't think that's actually part of the spec.
Arnaud,
I'm using 1.4.2, and the problem I had may not be the same as yours, but
see my messages "Unbound prefix after decryption".
In my case, the problem was that the DOM being passed for encryption id
not have the xmlns attribute set before it was processed. A
normalizeDocument() in the right
Peter B. West pbw.id.au> writes:
>
> Arnaud,
>
> I'm using 1.4.2, and the problem I had may not be the same as yours, but
> see my messages "Unbound prefix after decryption".
>
> In my case, the problem was that the DOM being passed for encryption id
> not have the xmlns attribute set before i
All,
why did it work with 1.4.0 and 1.4.1 then? Were these two version
buggy in that case? Or what was changed in 1.4.2 to get this
incompatible behaviour?
Because we use it in WSS4J we always rely on the backward compatibility.
Changing the WSS4J code just to circumvent a problem would cause a
https://issues.apache.org/bugzilla/show_bug.cgi?id=45586
Satish Burnwal <[EMAIL PROTECTED]> changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
