Re: FB JDBC version?
Re: FB JDBC version?
- Subject: Re: FB JDBC version?
- From: OCsite via Webobjects-dev <email@hidden>
- Date: Fri, 23 Aug 2024 17:05:49 +0200
Ramsey,
> On 23. 8. 2024, at 16:10, Ramsey Gurley <email@hidden>
> wrote:
> Check the startup logging in your app. I'm fairly sure a standard wonder app
> dumps the entire classpath as part of the start of the startup logging.
It does; that's where I've found my classpath is definitely OK. Alas, the
bloody Java ignores the classpath and happily loads the JDBC driver from
java.ext.dirs, regardless the classpath path :(
Thanks,
OC
>
> From: email@hidden <email@hidden>
> Sent: Friday, August 23, 2024 6:20 AM
> To: Ramsey Gurley <email@hidden>; WebObjects-Dev List
> <email@hidden>
> Subject: Re: FB JDBC version?
>
> Ramsey,
>
> looks like you are again right. Meantime I've investigated, and it looks like
> - the bloody Java, despite having an explicit path to the proper driver on
> classpath (I've checked in runtime logs, it's OK), still ignores it and loads
> another driver from java.ext.dirs;
> - where, I believe, a FrontBase driver should never be anyway, but some
> proactive admin seems to have put the old version to. Ick!
>
> Is there a decent way for a given JAR to log out a path from which it has
> been really loaded? I've tried to search Net, but did not found any. There
> are ways to find a path for a known class (but I do not know which classes
> there are in the FrontBase driver; and if I find a class they use now, it
> might fail in future if they change the names), and even those, based on a
> getProtectionDomain which might throw, are a bit complex to my liking...
>
> Thanks a lot!
> OC
>
>> On 22. 8. 2024, at 22:51, Ramsey Gurley <email@hidden
>> <mailto:email@hidden>> wrote:
>>
>> Are you sure you don't have more than one jdbc jar floating around in your
>> application build path? With ant, I forget how it determines which jar wins.
>> With maven, you can just open the pom.xml in eclipse and check in the
>> Dependency Hierarchy tab.
>> From: OCsite via Webobjects-dev <email@hidden
>> <mailto:email@hidden>>
>> Sent: Thursday, August 22, 2024 2:54 PM
>> To: WebObjects-Dev List <email@hidden
>> <mailto:email@hidden>>
>> Subject: FB JDBC version?
>>
>> Hi there,
>>
>> how does one properly determine the current FB JDBC driver version?
>>
>> Lately we were not sure whether all our installations contain the newest
>> release, and thus I've added a code to log out the version. The code I've
>> found — is there another, better, and more reliable variant? — looks like
>> this:
>>
>> ===
>> def eoa=EOAdaptor.adaptorWithModel(model)
>> def pin=eoa.plugIn()
>> logln "using driver $eoa.plugInName ${pin.jdbcInfo['DRIVER_VER']}"
>> ===
>>
>> The problem is, this code gives me different results (sometimes 2.5.10,
>> sometimes 2.5.9) for the very same frontbasejdbc.jar (which should really be
>> 2.5.20 — 240643 bytes, md5 72266d135712d26c60bc5cc1e1dc7c94). What do I
>> overlook?
>>
>> Thanks,
>> OC
>> Confidentiality Notice: This email, including all attachments and replies
>> thereto, are covered by the Electronic Communications Privacy Act, 18 U.S.C.
>> Sections 2510-2521 and are legally privileged. This information is
>> confidential, and intended only for the use of the individuals or entities
>> named above. If you are not the intended recipient, you are hereby notified
>> that any disclosure, copying, distribution or the taking of any action in
>> reliance on the contents of this transmitted information is strictly
>> prohibited. Please notify us if you have received this transmission in
>> error. Thank you.
>
> Confidentiality Notice: This email, including all attachments and replies
> thereto, are covered by the Electronic Communications Privacy Act, 18 U.S.C.
> Sections 2510-2521 and are legally privileged. This information is
> confidential, and intended only for the use of the individuals or entities
> named above. If you are not the intended recipient, you are hereby notified
> that any disclosure, copying, distribution or the taking of any action in
> reliance on the contents of this transmitted information is strictly
> prohibited. Please notify us if you have received this transmission in error.
> Thank you.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden