db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3451) Remove dependency between StandardException class and org.apache.derby.impl.jdbc classes.
Date Mon, 25 Feb 2008 04:58:51 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572013#action_12572013

Daniel John Debrunner commented on DERBY-3451:

I'm looking at committing this patch, I'll fix up the class name in the header in DerbySQLException.java
(it has a different class name there).

Just FYI - I think a longer term goal would be to remove EmbedSQLException and now DerbySQLException
and instead just use java.sql.SQLException.
JDBC 4 tends to lead in that direction because it has a number of sub-classes for SQLException
and I think it would be the wrong approach for Derby
to have an Embed version for every SQLException sub-class. The main reason originally for
EmbedSQLException originally was to be able to
keep the original non-SQLException (e.g. StandardException, IOException), which is (should
be?) now handled by Throwable.initClause().

Throwing a non-java library exception causes some issues for JMX as the exception can not
be transfered to the client.

> Remove dependency between StandardException class and org.apache.derby.impl.jdbc classes.
> -----------------------------------------------------------------------------------------
>                 Key: DERBY-3451
>                 URL: https://issues.apache.org/jira/browse/DERBY-3451
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: Dibyendu Majumdar
>            Assignee: Dibyendu Majumdar
>         Attachments: DERBY-3451_patch_rev630512.txt
> In the package org.apache.derby.iapi.error, the class StandardException contains references
to following classes:
> org.apache.derby.impl.jdbc.Util
> org.apache.derby.impl.jdbc.EmbedSQLException
> This is undesirable as it introduces a dependency between StandardException and the implementation
of EmbedSQLException.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message