That's the fix that I'm talking about. The DOM will store the non schema normalized value (when validation is on and the dom normalization feature is off).
Khaled
| "Scott Cantor"
<[EMAIL PROTECTED]>
02/08/2005 11:26 AM
|
|
> In the last version of Xerces-C, there was fix for the DOM
> normalization problem. When the feature is set to false,
> you'll get back the non schema normalized value. Is this
> still a problem for you?
That particular approach is not ideal (and it's a fairly old fix, not
recent), but more importantly, there was a change in 2.6 such that when
validation is on (and regardless of the data normalization setting), a
strict base64 validator is applied that cannot validate unnormalized base64
data. It has to do with checking the number of bytes to be a multiple of 4,
and the line breaks you leave in cause the multiple to be something else.
IOW, you can leave normalization on and break your signature, or leave it
off and fail to even validate.
I raised this problem and got a response that seemed to indicate the
solution was to fix Xerces to store off the normalized value in a "separate"
bucket for the schema validation step to use instead of overwriting the
actual DOM. That seems to be what XercesJ is doing, at least it appears to
actually support validation and normalization now without breaking
signatures.
I can probably find the thread if you like, but if you search for my
address, you should find it in the archives. I think I filed a bug on this,
but the problem is it's not precisely a bug, more of a mismatch between XML
specifications.
-- Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
