db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anurag Shekhar (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1140) Provide JDBC4 SQLException subclasses support in network driver
Date Wed, 22 Mar 2006 18:13:04 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1140?page=comments#action_12371445 ] 

Anurag Shekhar commented on DERBY-1140:

This patch is not ready to be considered for commit yet. I have uploaded it to get comments
about it and to discuss the SecurityException I am getting while running the test suite.

The class org.apache.derby.shared.common.error.ExceptionUtil40.getSQLExceptionFromState is
present in derby.jar and derbyclient.jar. While running the test suite with framework set
to DerbyNetClient both of the jars needs to be in classpath. When harness tries to execute
the test case its loading the class from derby.jar and gets SecurityException because the
package is sealed. Changing the order of jar files also doesn't help (in that case the starting
network framework fails because of same exception).

I am getting this problem while running the test suite only. The standalone network client
 connecting to a network server works fine.

I can't think of any good solution to solve this problem but I have two bad solutions

1.Drop the Exception40 and move the code to individual exception factories
2.Mark the package as not sealed (I am sure this shouldn't be done specially because the problem
exist while running the test suite only.)

> Provide JDBC4 SQLException subclasses support in network driver
> ---------------------------------------------------------------
>          Key: DERBY-1140
>          URL: http://issues.apache.org/jira/browse/DERBY-1140
>      Project: Derby
>         Type: Sub-task
>     Versions:
>  Environment: jdk1.6 
>     Reporter: Anurag Shekhar
>     Assignee: Anurag Shekhar
>  Attachments: derby-1140.diff

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message