On Tue, 2004-12-21 at 11:12, Scott Cantor wrote:
> Note that this assumes you're validating, not just parsing. Parsing alone
> should *not* have the affect you're seeing, and that flag will mean nothing
> unless schema validation is on. Just checking.
I am indeed validating. I've found a workaroun
> Argh. Okay, I've switched to using the DOM3 calls to parse the XML, but
> I can't work out which particular DOMConfiguration setting to use to
> stop this from happening. Do you know which particular one does it?
> Setting datatype-normalization to false doesn't seem to cut it...
Hmm, that shoul
On Mon, 2004-12-20 at 06:15, Scott Cantor wrote:
> Are you validating the document while parsing it? If so, the only "fix" is
> to turn off data type normalization. With that enabled, which is the
> default, there is no way to prevent this behavior because it is mandated by
> the XSD spec.
Argh. O
I just paid attention that in OpenSSLCryptoKeyRSA::OpenSSLCryptoKeyRSA
(somewhere near line 143) when copying RSA key from EVP_PKEY, member
m_keyType is not initialized.
I didn't look deep into code and don't know what possible implications
this might cause (seems that nothing serious at all), but
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project xml-security has an issue affecting its community integration.
This issue affects
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project xml-security has an issue affecting its community integration.
This issue affects
