Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <2018816228.1121283850264.JavaMail.jira@ajax.apache.org>
Date: Wed, 13 Jul 2005 21:44:10 +0200 (CEST)
From: "Daniel John Debrunner (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-289) Enable code sharing between Derby
 client and engine
In-Reply-To: <1175913042.1116266884833.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12315775 ] 

Daniel John Debrunner commented on DERBY-289:
---------------------------------------------

In case it's not clear, this is the type of situation I'm talking about.

Application A is a client server application and requires Derby client 10.2

Application B is a local embedded Derby application and requires Derby engine 10.3

Now I want to run a client to A  and B in the same JVM for some reason, maybe portlets, maybe multiple applications
in the same app server, maybe application B requires access to application A.

This would be supported with the current model, complete flexibility because the code bases are separate.

So do we want to lose this flexibility, or support it with the shared code model?

Some side history, we did do some work at IBM for Cloudscape prior to open sourcing that ensured that the tools (ij mainly) did not have to be at the same version as the engine, basically by ensuring there was no code in common. This was a request from our customers.


> 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: 10.0.2.1, 10.0.2.0, 10.0.2.2, 10.1.1.0
>  Environment: N/A
>     Reporter: David Van Couvering
>     Priority: Minor
>      Fix For: 10.2.0.0

>
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira