db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: [jira] Updated: (DERBY-668) SysInfo can give misleading information when JDBC jars are loaded from jre/lib/ext
Date Wed, 23 Nov 2005 22:58:52 GMT
Bryan Pendleton (JIRA) wrote:

>     [ http://issues.apache.org/jira/browse/DERBY-668?page=all ]
>
>Bryan Pendleton updated DERBY-668:
>----------------------------------
>
>    Attachment: derby-668-2.diff
>
>Hi Kathey,
>
>I re-worked my patch based on your comments, and I think it is more useful now. I abstracted
the code out into a subroutine so that it could be shared, added some comments, and, most
importantly, used the code in the "sysinfo -cp" code path, where it actually makes a lot more
sense and is more useful.
>
>The net effect of this patch is:
>1) If you run "sysinfo -cp" (and any of its variants), sysinfo now reports the actual
location where the class was loaded from, in addition to telling you whether or not it loaded
the class successfully.
>2) If you run just "sysinfo", when it is processing the db2jcc.jar file in your classpath,
it now reports the actual location where the DB2Driver class was loaded from, which may not
be the db2jcc.jar file in your classpath (if you've placed db2jcc.jar somewhere else).
>
>Please have a look at this new patch when you get a chance and tell me what you think.
>
>  
>
It looks good to me and should make it easy to expand to the other
jars.  Is the  file:[jarName]!className format known to be consistant 
across platforms?   That is the only part about it that makes me a bit
nervous. 






Mime
View raw message