Not at all an answer to the original question but more of a comment on your
dev. setup. My personal experience is that you should aim at having the
development environment as close as possible to the production environment.
If you develop your app on JBoss and Tomcat, you may spend lots of time
trying to make it work on WebSphere at the end. So my advice is really to
make sure you test your application on the target platform as soon as
possible, or at least very early in the process and regularly.
Fr.
-----Original Message-----
From: Luis Olivares [mailto:[EMAIL PROTECTED]]
Sent: 18 September 2001 17:17
To: [EMAIL PROTECTED]
Subject: Re: The final word on struts and jboss 2.2.2 and tomcat 3.2.2
Im too very interested in this topic, since we'll be developing an
Application for WebSphere 4.0, but our Development Enviroment will be Jboss
with Tomcat.
Regards.
Luis Olivares.
[EMAIL PROTECTED]
--------------------------------------------------------------
"Intelligence is the ability to avoid doing
work, yet getting the work done"
--Linus Torvalds--
----- Original Message -----
From: "bill milbratz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, September 18, 2001 9:36 AM
Subject: The final word on struts and jboss 2.2.2 and tomcat 3.2.2
> I'd like to confirm from the Struts Authorities, that indeed, struts
> doesn't quite-work-right with tomcat 3.2.2 and jboss 2.2.2. (Classloader
> problems and sundry "'class not found" exceptions). Does jboss-2.4.1a and
> Tomcat-3.2.3 solve the problem?
>
> I've seen a few posts on this topic:
>
> This one suggests that Tomcat 3.3 makes the problem disappear:
> http://www.mail-archive.com/[email protected]/msg14601.html
>
> This one suggests a workaround which involves precompiling the jsp pages:
> http://www.mail-archive.com/[email protected]/msg12335.html
>
> This one suggests dropping back to tomcat 3.2.1
> http://www.mail-archive.com/[email protected]/msg12400.html
>
>
> thanks in advance,
>
> bill m
************************************************************************
The information in this email is confidential and is intended solely
for the addressee(s).
Access to this email by anyone else is unauthorised. If you are not
an intended recipient, you must not read, use or disseminate the
information contained in the email.
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Capco.
http://www.capco.com
***********************************************************************
