db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-289) Enable code sharing between Derby client and engine
Date Fri, 15 Jul 2005 18:48:10 GMT
    [ http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12315943 ] 

Kathey Marsden commented on DERBY-289:

As for the mixed versions, I would like to understand how we would recommend upgrading in
a situation where the jvm in question has both server and client to talk to remote servers
in a failover situation or whatever.  So I have 100 nodes each with client and server talking
to each other.
Typically you might tell me.

1) upgrade all your servers.
2)  upgrade your clients and application to use the new functionality.

So at least for some period of time there would be a mix of versions.  Theoretically if we
guarantee full backward/forward compatibility,  I  could use my old application with the new
client for some period of time, but that would be a burdon because I  would have to test my
 old application with the new client and who wants to spend time on that.

So how would I upgrade in this scenario?

> 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