db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-289) Enable code sharing between Derby client and engine
Date Tue, 08 Nov 2005 23:08:23 GMT
    [ http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12357094 ] 

Rick Hillegas commented on DERBY-289:

o Yes, please. Please move SQLState.java to common.

o CommonFeatures doesn't seem to provide much value. Could it be merged into SharedComponentInfo?

o I'm curious about the catching of ShutdownException in MessageServices after calling MessageUtil.getCompleteMessage().
Do you understand how this exception is raised?

o You might want to hold off on this submission until you check in my compatibility test patch
which moves the JUnit tests under their own subdirectory in the code tree. That will avoid
the nasty svn-moving of your tests.

> Enable code sharing between Derby client and engine
> ---------------------------------------------------
>          Key: DERBY-289
>          URL: http://issues.apache.org/jira/browse/DERBY-289
>      Project: Derby
>         Type: Improvement
>   Components: Network Client
>     Versions:,,,
>  Environment: N/A
>     Reporter: David Van Couvering
>     Assignee: David Van Couvering
>     Priority: Minor
>      Fix For:
>  Attachments: DERBY-289.diff
> Right now, there is no way for the Derby network client to share code with the Derby
engine.  We should have a separate jar file, e.g. derby_common.jar, that contains shared code
and is used by both the client and the engine.  

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