managing mulitple 'servlet.jar' versions ... which one does WO require?
managing mulitple 'servlet.jar' versions ... which one does WO require?
- Subject: managing mulitple 'servlet.jar' versions ... which one does WO require?
- From: OpenMacNews <email@hidden>
- Date: Mon, 28 Feb 2005 20:28:56 -0800
hi all,
i'm building/using ProjectWonder's frameworks as an add-on to a 'standard'
WO5.2.3 install on OSX 10.3.8 + DevTools.
in building the frameworks, the project requires the presence of 'servlet.jar'
in the default ClassPath, i.e. in /Library/Java/Extensions/
to that end, I:
% cp /Library/WebObjects/Extensions/servlet.jar
/Library/Java/Extensions/servlet.jar
where,
% ls -al /Library/WebObjects/Extensions/servlet.jar
-rw-rw-r-- 1 devuser admin 78064 Mar 1 2004
/Library/WebObjects/Extensions/servlet.jar
is from the default WO install.
however, i've a number of other "servlet.jar"s on my system:
(a) # from an Eclipse 3.x IDE install
-rw-r--r-- 1 devuser admin 79265 Sep 16 09:11
/Volumes/Develop/IDEs/eclipse/plugins/org.eclipse.tomcat_4.1.30/servlet.jar
(b) # from the Apple dev tools installs
-rw-rw-r-- 1 devuser admin 80054 Mar 19 2003
/Library/Tomcat/common/lib/servlet.jar
-rw-rw-r-- 1 devuser admin 78064 Oct 30 2002
/Developer/Java/J2EE/jakarta-servletapi-4/lib/servlet.jar
(c) # from a Tomcat v5.6.7 install
-rw-r--r-- 1 devuser admin 97693 Jan 19 12:40
/usr/local/javadev/tomcat/common/lib/servlet-api.jar
my PREFERENCE is to use a single/consistent instance of servlet.jar across my
projects, and that it be (c), above, from the Tomcat v5.6.7 binary install ...
unfortunately, Wonder (as an e.g.) does not build (4 me) successfully with
anything other than the WO v5.2.3's standard install servlet.jar; use of other
versions causes as-yet-not-figured-out 'nested exceptions' in my ant build
output.
my (as yet feeble) understanding from the fine folks at the Wonder project is
that this servlet.jar 'version sensitivity' is an Apple issue:
>> (1) Does ProjectWonder presume/require a particular, old, servlet.jar?
>
> Dunno. Any special lib will be the one that WOServletContext needs and
> inherits from - which is an Apple class...
...
>> (3) Is there any effort currently underway to migrate Wonder to
>> compliance/compatibility with a newer servlet api? specifically, the
>> Tomcat v5.5+ apis?
>
> Ask Apple. From where I stand, we might as well thrash ERXServletContext and
> move that stuff over to ERXWORequest or the thread storage or wherever. This
> wouldn't solve your problem, though, as then you'd need to tackle the Apple
> class directly... ask Apple.
sooooo, I'm hoping here for a little education. towit,
####################
## QUESTION(s)
#
(1) what "pain & agony" might I cause myself if I have multiple servlet.jars in
my default classpath? specifically, one "old" for Wonder, and one "newer" for
my other projects? or, should I simply remove all from the DEFAULT paths, and
specify particular versions/targets in per-project properties files?
(2) WHAT might the 'Apple issue', mentioned above, *BE* ? My *guess*, at this
stage, is that the servlet APIs have changed, but --methinks -- that would mean
that Wonder would have to migrate to the new API calls/inheritance.
(3) Does, in fact, Apple's WebObjects itseld *presume* the presence of a
particular servlet.jar version? i'd a thunk that was an APPLICATION issue ...
just trying to 'grok' the right question(s) to start with ...
thanks!
richard
_______________________________________________
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