I doubt it is a digesting problem, since that just uses the underlying
JCA SHA1 MessageDigest provider code. It is more likely to be that for
whatever reason the pre-digested content is different for some reason.
Perhaps the XML is being modified by the server and that breaks the
signature. You
Can you please resend your message to [EMAIL PROTECTED] ?
Although the JSR 105 XMLDSig implementation delivered with JWSDP is
based on Apache XMLSec, this alias is not the correct place to ask
questions about JWSDP.
Also, please upgrade to JWSDP 1.4 and let me know if you still see the
problem
