[
https://issues.apache.org/jira/browse/DERBY-7063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008130#comment-17008130
]
sagar commented on DERBY-7063:
------------------------------
Ok so managed to connect to 10.15.1.3 using squirrel. Put derbyClient
derbyTools and derbyshared jar files in the squirrel lib folder.
So that closes this report.
Also the network server runs well with the startNetworkServer scripts ...
upgraded and old database and tried out an existing application ... all well ...
Just wanted to know if a new derby release is coming up by March, since its
will be a year since the 10.15.1.3 has released.
> Cannot connect using squirrel 3.3.0
> -----------------------------------
>
> Key: DERBY-7063
> URL: https://issues.apache.org/jira/browse/DERBY-7063
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Server
> Affects Versions: 10.15.1.3
> Reporter: sagar
> Priority: Major
>
> The derbyclient.jar file does not have the
> org.apache.derby.jdbc.ClientDriver.class
>
> When I add the jar file in squirrel, ssquirrel automatically detects the
> driver but since this class is missing it does not detect it.
> Till now I was using 10.11.1.1 database. Now I have decided to upgrade and
> this issue cropped up.
>
> Yes Derby has switched to the module system from 10.15.1.3 but the derby
> documentation mentions connection to Network Server similar to previous as
> using the
> org.apache.derby.jdbc.ClientDriver and this class is missing from the new
> derbyclient.jar.
>
>
> Squirrel is running on Java 1.8
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
