Exactly my point. org.apache.xml.serialize.XMLSerializer,OutputFormat is used ONLY in
one file
namely XMLCipher.java. We are better off gaining compatability with any JAXP
compatible parser. We
are forcing people to use a specific xerces version EVEN if they have other parsers in
their
environm
Surely it's better to say "if you have this bug then download a version of
Xerces greater than x.x" rather than "fixing" a bug in someone else's code
with a hack in yours? That's just asking for maintenance headaches isn't
it?
Well.. right now we are dependent on Xerces for a single tiny Xerces-onl
--
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: 03 February 2004 15:11
To: [EMAIL PROTECTED]
Subject: Re: AW: AW: AW: Verification after decrypt
Werner,
We can't depend on a specific version of Xerces EVEN if they fix problems in
their code. So is
there a possibility of patching xml-se
atter function with new patch)
Regards,
Werner
> -Ursprüngliche Nachricht-
> Von: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 3. Februar 2004 16:11
> An: [EMAIL PROTECTED]
> Betreff: Re: AW: AW: AW: Verification after decrypt
>
>
> Werner,
>
Werner,
We can't depend on a specific version of Xerces EVEN if they fix problems in their
code. So is
there a possibility of patching xml-security itself? (Write custom serializers just
like we do in
Axis)
thanks,
dims
--- Dittmann Werner <[EMAIL PROTECTED]> wrote:
> Berin,
>
> AFAIK Dims w
Berin,
AFAIK Dims wrote an e-mail to somebody of the
Xerces group and asked if they would fix the problem.
Don't know about the outcome.
After all, the Xerces guys are heavily working
on the serialization matter. But i'm not
aware if they fix it soon.
BTW, the Xerces Bugzilla # 25853 describes t
