[
https://issues.apache.org/jira/browse/DERBY-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041052#comment-13041052
]
Robert Lieb commented on DERBY-4961:
------------------------------------
If the sysinfo class always returns the embedded version, why is
DBMS.properties than not in the derbyclient jar file. This would solve the
problem and is compline to the API.
> org.apache.derby.tools.sysinfo return wrong minor & major versions if
> ClientDriver is used
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-4961
> URL: https://issues.apache.org/jira/browse/DERBY-4961
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.7.1.1
> Reporter: Juraj Burian
>
> I am not sure that this is a bug.
> Hibernate uses code like this:
> final Class sysinfoClass = ReflectHelper.classForName(
> "org.apache.derby.tools.sysinfo", this.getClass() );
> final Method majorVersionGetter =
> sysinfoClass.getMethod( "getMajorVersion", ReflectHelper.NO_PARAM_SIGNATURE );
> final Method minorVersionGetter =
> sysinfoClass.getMethod( "getMinorVersion", ReflectHelper.NO_PARAM_SIGNATURE );
> driverVersionMajor = ( (Integer)
> majorVersionGetter.invoke( null, ReflectHelper.NO_PARAMS ) ).intValue();
> driverVersionMinor = ( (Integer)
> minorVersionGetter.invoke( null, ReflectHelper.NO_PARAMS ) ).intValue();
> The problem is that if ClientDriver is used, this code returns -1, -1 instead
> of correct version numbers.
> Hibernate checks versions and if not correct numbers returned, then exception
> is raised (versions are checked when sequence is used - so it is new feature
> for both of sides :-) )
> I tried test this by hands and achieved the same behavior.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
