Thanks for the info Lars and Vladimir,
Looks like they use older version that does not contain the additions you
mentioned...
Best regards,
Per
On Wednesday 12 February 2003 15.20, Lars Martin wrote:
> >>I have noticed a lot of code like:
> >>
> >>} catch (Exception e) {
> >> throw new XMLDBException( blah, e.getMessage() );
> >>}
> >>
> >>which is really hard to work with when debugging, as most of
> >>the information about the exception is lost.
>
> Of course, they don't use the chained exception mechanism I implemented
> for XMLDBException...
>
> from the XMLDBException class definition:
>
> public XMLDBException (int errorCode, Throwable cause) {
> this(errorCode, 0, "", cause);
> }
>
> public XMLDBException (int errorCode, String message, Throwable cause)
> { this(errorCode, 0, message, cause);
> }
>
> public XMLDBException (int errorCode, int vendorErrorCode, Throwable
> cause) {
> this(errorCode, vendorErrorCode, "", cause);
> }
>
> public XMLDBException (int errorCode, int vendorErrorCode, String
> message, Throwable cause) {
>
> >>Has use of a cascading exception class been considered?
>
> Well, it looks like it was...
>
> they just have to change their code with:
>
> throw new XMLDBException(e.errorCode, e.vendorErrorCode, blah, e);
>
> -Vladimir
----------------------------------------------------------------------
Post a message: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Contact administrator: mailto:[EMAIL PROTECTED]
Read archived messages: http://archive.xmldb.org/
----------------------------------------------------------------------
