db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-415) sysinfo with -cp client option should not print error saying DB2 jar file and driver class are missing
Date Tue, 15 Aug 2006 23:55:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-415?page=comments#action_12428270 ] 
            
Bryan Pendleton commented on DERBY-415:
---------------------------------------

Here's a short release note to describe the new behavior:

PROBLEM: Scope of the "-cp client" argument to the Sysinfo tool was too broad.

SYMPTOM: If you run "java org.apache.derby.tools.sysinfo -cp client SimpleApp.class" you get
a message indicating that the DB2 JCC driver was not found in your classpath, even though
you have the Derby Client library in your classpath.

CAUSE: The implementation of the "-cp client" argument in the Sysinfo tool was checking for
both the Derby Client jar and the DB2 JCC driver jar, and was reporting an error if either
jar was missing. Since the Derby Client jar is the preferred client to use, the Sysinfo tool
no longer needs to check for the presence of the DB2 JCC driver jar in this case.

SOLUTION: The implementation of the "-cp client" argument has been modified to check only
for the presence of the Derby Client jar. To check for the presence of the DB2 JCC driver
jar, you can pass the new "-cp db2driver" argument.


> sysinfo with -cp client option should not print error saying DB2 jar file and driver
class are missing
> ------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-415
>                 URL: http://issues.apache.org/jira/browse/DERBY-415
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 10.1.1.0
>            Reporter: David Van Couvering
>         Assigned To: Bryan Pendleton
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         Attachments: derby-415-cp-db2driver.diff, derby-415.diff
>
>
> If you run
>   java org.apache.derby.tools.sysinfo -cp client SimpleApp.class
> you get
> FOUND IN CLASS PATH:
>     Derby Client libraries (derbyclient.jar)
>     user-specified class (SimpleApp)
> NOT FOUND IN CLASS PATH:
>     Derby Client libraries (db2jcc.jar)
>     (com.ibm.db2.jcc.DB2Driver not found.)
> The "NOT FOUND IN CLASSPATH" output is confusing and invalid because we're testing the
network client, not the DB2 JCC client.

-- 
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

        

Mime
View raw message