db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-289) Enable code sharing between Derby client and engine
Date Wed, 13 Jul 2005 00:13:11 GMT
    [ http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12315645 ] 

Daniel John Debrunner commented on DERBY-289:

I think any shared solution needs to handle mixing of client and server/engine versions. E.g.
assuming shared code is added in 10.2, an application could be using a local 10.2 derby engine
 but using a 10.3 client to talk to a remote derby engine, all from the same JVM. Apart from
mismatched classes, it's also hard to guarantee which common code is loaded, the 10.2 or the
10.3, usually depends on class path order. Thus you may have  handle the common code be at
a lower or higher level than expected.

As for a single server side jar, that forces the network server overhead on simple embedded
users, and may add a security concern they don't want to have, basically code that listens
on a network port. Even having the code in the jar may of concern, even if they never start

> 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