On Jan 30, 2007, at 6:20 AM, Kieran Kelleher wrote:
> I only use it for JDBC drivers, but I thought it might be a
> workaround for Lachlan.
It is OK (actually the intended location) for JDBC drivers. For
anything other than extensions to the core Java API, it is a
dangerous place to put things. Pay attention to Anjo's warning. The
problems that it can cause are very, very hard to debug.
> A better development strategy is putting the jars in a framework in
> any case ..... so that might be a good opportunity for those moving
> to Eclipse to refactor and organize their 3rd party jars better.
> IMHO, adding a framework to a project is not that much work unless
> you are spitting out projects at a rate of one per hour.
That still leaves you with a similar problem unless you also clean
out /Library/WebObjects/Extensions on each machine. IIRC, the jars
there are loaded first (by the WO launch script) so they will take
precedence over anything in a framework. Any way that you do it, it
is messy.
Chuck
>
> On Jan 30, 2007, at 7:58 AM, Anjo Krank wrote:
>
>> Am 30.01.2007 um 13:43 schrieb Kieran Kelleher:
>>
>>> Does /Library/Java/Extensions give you the behaviour you want
>>> instead of /Library/WebObjects/Extensions ?
>>
>> Putting stuff there is even more dangerous due to the limits on
>> class loading imposed. Use it with *extreme* caution and don't
>> complain if stuff isn't working.
>>
>> Cheers, Anjo
>>
>>
>
>
--Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
This archive was generated by hypermail 2.0.0 : Tue Jan 30 2007 - 12:51:12 EST