db-derby-dev mailing list archives

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

David Van Couvering commented on DERBY-289:

Thanks for your comments, Dan.

Can you explain to me how a classloader can load a 10.2 shared class for the client code and
a 10.3 shared class for the server?  Isn't the classpath the same, so you end up picking up
the same class either way?  Assuming this is possible, is this something we actually want
to try and handle?  I could see doing two versions under two different classloaders, with
different classpaths, to support online upgrade -- but within the same Derby system/classloader?
 It seems if anything, I should catch a version mismatch and throw an exception, but do we
really want to try and make this work?  Can you give me a scenario where this is useful/desirable?

Regarding the jar files, I see your point: jars are units of security.  Why expose an embedded
user to the risks of network code unnecessarily.  I'll rescind my suggestion.



> 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