Re: /Library/WebObjects/Extensions
Re: /Library/WebObjects/Extensions
- Subject: Re: /Library/WebObjects/Extensions
- From: Chuck Hill <email@hidden>
- Date: Fri, 24 Oct 2008 12:56:07 -0700
On Oct 24, 2008, at 12:42 PM, Ricardo J. Parada wrote:
How about jars that WebObjects installs in /Library/WebObjects/
Extensions? i.e. the following:
avalon-framework-4.1.2.jar log4j-1.2.4.jar
axis-ant.jar logkit-1.0.1.jar
axis.jar saaj.jar
commons-discovery-0.2.jar serializer.jar
commons-logging-1.0.4.jar servlet.jar
derby.jar wsdl4j-1.5.1.jar
derbyclient.jar xalan.jar
jaxrpc.jar xercesImpl.jar
log4j-1.2.14.jar xml-apis.jar
Bad, bad, all bad. If you use them, take them out. Take them all out
and you will quickly know which ones you use. :-)
Notice that you already have a problem with both log4j-1.2.4.jar and
log4j-1.2.14.jar in that directory! Which gets used?
Chuck
On Oct 24, 2008, at 3:34 PM, Chuck Hill wrote:
On Oct 24, 2008, at 12:18 PM, Ricardo J. Parada wrote:
Hi,
I'm recommending that we place third party jars in a framework.
The for projects that need them then simply add the framework to
the class path.
Good idea.
I'm recommending that as a better solution to putting the third
party jars in /Library/WebObjects/Extensions.
/Library/WebObjects/Extensions is a Very Bad Idea that looks like a
good idea.
I remember that as a best practice although I'm not 100% clear on
the benefits. I listed the following. Please someone correct me
if I'm wrong or missing something:
------------
The problem with jars in /Library/WebObjects/Extensions is that
they are loaded whether you want / need them or not. They may
cause conflicts if you open a project that already has that jar in
it or one of its frameworks. You are not managing those
dependencies from eclipse as you should. You may deploy an app
that works well in your development environment and then find out
at deployment time that it needs a jar that you had in your /
Library/WebObjects/Extensions.
You don't have these problems if you put the jars in a framework
and then add the framework to the class path of the project that
needs the classes in the jars.
-----------
Is this accurate? Am I missing something? :-)
There is also the benefit of being able to deploy multiple apps
that need different versions of the jars in /Library/WebObjects/
Extensions. If you are using anything from /Library/WebObjects/
Extensions then you are not managing dependancies. That is never
good.
Chuck
--
Chuck Hill Senior Consultant / VP Development
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
--
Chuck Hill Senior Consultant / VP Development
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
_______________________________________________
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