db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Van Couvering <David.Vancouver...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-289) Enable code sharing between Derby client and engine
Date Fri, 15 Jul 2005 17:40:39 GMT
Great minds think alike, Dag, I'm investigating using multiple
classloaders.  There are a lot of tricky questions around the side
effects of doing this that I am trying to formulate and then either
answer or pose to the group.  Still in the "cosmic ooze" phase of
thought at this point, nothing really solid has formed yet...

David

Dag H. Wanvik wrote:
> Hi,
> 
> Isn't the "right" way to handle different versions of the same code in
> one VM to use classloaders? I know in one product we have internally,
> we cater for upgrades in this way. Don't app servers do this as well,
> to insulate apps' use of libraries? Two different versions of the
> client driver inside one VM would need to be handled in this way, so
> when embedded (v2) and client (v1) works without any such measure
> p.t., it doesn't really solve all use cases anyway..? 
> 
> Dag
> 
> 
> 
>>>>>>"RH(" == Rick Hillegas (JIRA) <derby-dev@db.apache.org> wrote:
> 
> RH(> 
> RH(>     [ http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12315870
] 
> RH(> Rick Hillegas commented on DERBY-289:
> RH(> -------------------------------------
> RH(> 
> RH(> 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?
> RH(> 
> RH(> > Enable code sharing between Derby client and engine
> RH(> > ---------------------------------------------------
> RH(> >
> RH(> >          Key: DERBY-289
> RH(> >          URL: http://issues.apache.org/jira/browse/DERBY-289
> RH(> >      Project: Derby
> RH(> >         Type: Improvement
> RH(> >   Components: Network Client
> RH(> >     Versions: 10.0.2.1, 10.0.2.0, 10.0.2.2, 10.1.1.0
> RH(> >  Environment: N/A
> RH(> >     Reporter: David Van Couvering
> RH(> >     Priority: Minor
> RH(> >      Fix For: 10.2.0.0
> RH(> 
> RH(> >
> RH(> > 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.  
> RH(> 
> RH(> -- 
> RH(> This message is automatically generated by JIRA.
> RH(> -
> RH(> If you think it was sent incorrectly contact one of the administrators:
> RH(>    http://issues.apache.org/jira/secure/Administrators.jspa
> RH(> -
> RH(> For more information on JIRA, see:
> RH(>    http://www.atlassian.com/software/jira
> RH(> 


Mime
View raw message