db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3782) Client Configuration.java imports engine class org.apache.derby.iapi.services.info.JVMInfo
Date Thu, 18 Sep 2008 21:02:44 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632383#action_12632383
] 

Myrna van Lunteren commented on DERBY-3782:
-------------------------------------------

I see two approaches for this:
a. copy the relevant code from org.apache.derby.iapi.services.info.JVMInfo into the method
needing it in org.apache.derby.client.am.Configuration
b. copy the entire JVMInfo class to package org.apache.derby.client.am

> Client Configuration.java imports engine class  org.apache.derby.iapi.services.info.JVMInfo

> --------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3782
>                 URL: https://issues.apache.org/jira/browse/DERBY-3782
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.5.0.0
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: DERBY-3782_a.diff, DERBY-3782_b.diff
>
>
> The client code (org.apache.derby.client.am.Configuration) imports the engine class org.apache.derby.iapi.services.info.JVMInfo.
> This will make two copies of the class in derby.jar and derbyclient.jar which can cause
problems if mixed version jars are used and  I think may cause jar sealing issues as well.
> Until we have a good framework for sharing code between engine and client, the client
shouldn't import engine classes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message