Caldarale, Charles R wrote:
That was already specified: the OP wants to compile servlets; nothing beyond a
JDK is needed.
- Chuck
Everything said about J2EE, classpaths etc is perfectly correct.
However, the other thing the OP said was that they want to use Eclipse
on a Mac. To build we
> From: NBW [mailto:email...@gmail.com]
> Subject: Re: J2EE on Mac
>
> The statement "installing JEE usually causes problems"
> implies JEE is something apart from Tomcat that doesn't
> play well with it.
There's no such implication; unfortunately, new users
A system wide CLASSPATH is a bad idea to begin with. Keep you classpath
scoped to you application/application server and you will never have this
issue.
On Mon, Feb 23, 2009 at 9:52 AM, Martin Gainty wrote:
>
> as chuck mentioned you have 2 different environments that deploy web
> archives
> If
Tomcat is not J2EE, and Glassfish is not J2EE. J2EE is a set of specs.
Tomcat contains implementations of some of them. Glassfish happens to bundle
implementation of all of them. Tomcat provides a piece of the EE stack,
installing the Glassfish application server bundle will you get one
implementat
as chuck mentioned you have 2 different environments that deploy web archives
If you absolutely positively need GF (which I do) then keep it on a separate
drive and do NOT
place common servlet*.jar on system classpath
you want to avoid GF and TC contending for the same resource(servlet<-api>.jar
> From: Mighty Tornado [mailto:mighty.torn...@gmail.com]
> Subject: Fwd: J2EE on Mac
>
> Can somebody please tell me where I can download the latest
> J2EE for Mac?
You do not need or want J2EE in order to compile servlets (and JSPs); the
regular JDK is enough.
Since you state Tomcat is already
