[
https://issues.apache.org/jira/browse/DERBY-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632402#action_12632402
]
Kathey Marsden commented on DERBY-3782:
---------------------------------------
Option c might be to use reflection to determine if one of the JDBC 4.0 methods
exists, so that the JVM version information is not needed. I see what you
mean though about there already being a problem with JVMInfo and sysinfo and
maybe this is not worth fixing because of that. I guess I don't have a strong
opinion.
> 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.
