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 Thu, 14 Jul 2005 23:20:10 GMT
    [ http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12315870 ] 

Rick Hillegas commented on DERBY-289:

I confess I'm still puzzled. It seems to me there may be two separate issues here: 1) the
interoperability of different derby versions across a network and 2) the coherence of derby
code running in a single VM. I'm all in favor of interoperability. But mixing and matching
derby versions in the same VM puzzles  me. I wonder whether we are talking about an edge case
here. Is that edge case worth not sharing utility libraries across derby?

> 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
>     Priority: Minor
>      Fix For:

> 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