Berin,
because the serializer code uses (or could be enabled) to use different
serializer methods (c14n, Xerces) and they all throw different exceptions
we either need to re-map the exception or let them ripple thru. The code
as it stand forwards the different exceptions to the caller.
Quite some functions inside XMLCipher call serializer methods either
directly od indirect.
Regards,
Werner
----- Original Message -----
From: "Berin Lautenbach" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, February 07, 2004 5:58 AM
Subject: Re: DO NOT REPLY [Bug 26660] - Replace Xerces specific code with
C14n instance
> Werner/Dims,
>
> Just went through it - one quick question before I apply.
>
> Why have a number of the "throws" statements been changed from
> "XMLEncryptionException" to "Exception"? I know this makes coding the
> library easier, but at the same time it clouds things up for the end
> user? (And I can't see anywhere where anything other than XMLEncryption
> Exception exceptions are being thrown.)
>
> As an example from the patch :
>
> private Document encryptElement(Element element) throws
> - XMLEncryptionException {
> + /* XMLEncryption */Exception {
>
> Cheers,
> Berin
>
>
> [EMAIL PROTECTED] wrote:
>
> > DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
> > RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
> > <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26660>.
> > ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
> > INSERTED IN THE BUG DATABASE.
> >
> > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26660
> >
> > Replace Xerces specific code with C14n instance
> >
> >
> >
> >
> >
> > ------- Additional Comments From [EMAIL PROTECTED] 2004-02-06
04:08 -------
> > guys,
> >
> > please apply this patch....
> >
> > -- dims
> >
> >
>
