it will only hurt your performance.
- Original Message -
From: "Berin Lautenbach" <[EMAIL PROTECTED]>
To:
Sent: Thursday, June 09, 2005 7:04 AM
Subject: Re: Canonical Transformation
> Should do it by default. Having said that - it wouldn't hurt to add the
> C14n transformation explici
Thanks for the quick response.
I could not reproduce the error yet, and I doubt it will be possible to
do it, since it never
happend before.
maybe the RAM of the system is unstable.
Raul Benito wrote:
Hi Michael,
It looks weird too me, it seems more a xerces problem than xml-sec.
But is goin
Hi Michael,
It looks weird too me, it seems more a xerces problem than xml-sec.
But is going to be a really tiring bug hunting, can you try to
reproduce with a simplest possible code, and send to us as a
testcase?.
This way we can test ourselves and send the bug to xerces if possible.
Regards,
Hi Berin,
you're absolutely right, and I understand it. If it was a requirement to
use CDATA tags for text nodes, we wouldn't have such problems. All other
contents could be considered subject to change. However, i'm using
Castor and it seems that the deserialisation process (marshalling)
rem
Hello,
I noticed a very strange behavior during a stresstest of our application.
after several days of runtime this stacktrace below occured. I have
never seen this before
and the application is in use for nearly two years now.
is there any known bug that causes this ?
we use xmlsecurity v1.2.1
Mike Haller wrote:
i don't know why Canonicalization doesn't address this problem at all.
It sounds like being incomplete to me. One the one hand, there is taken
effort to "normalize" the XML document so it can be signed to
avoidproblems with formattings - on the other hand something simple li
Yes Berin, thanks,
i don't know why Canonicalization doesn't address this problem at all.
It sounds like being incomplete to me. One the one hand, there is taken
effort to "normalize" the XML document so it can be signed to
avoidproblems with formattings - on the other hand something simple li
Should do it by default. Having said that - it wouldn't hurt to add the
C14n transformation explicitly for all references.
Cheers,
Berin
Marina Moreno wrote:
Hi,
I have read in XML-Signature Syntax and Processing W3C recommendation,
section 4.3.3.2 The Reference Processing Model, "
Mike Haller wrote:
But after some marshalling/unmarshalling with Castor, the resulting
Document has no newlines any more, hence the SignatureValue of the
SignedInfo element is invalid.
How do I tell XMLSignature to add newlines into the SignedInfo before
validation? Or should I remove the ne
