Personally, I would suggest autodeploying on the production/test
platform from the CVS daily, as is done on Jakarta, and then running a
suite of Unit and application tests. This can give you much more leeway
over what platform developers use. However, it is of course vital that
the production/test platform be as close to the production target
platform as possible (software, hardware, DBMS), and that the latest
Unit and application tests be run every workday.
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel +1 716 737-3463
-- http://www.husted.com/about/struts/
Rey Francois wrote:
>
> 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/struts-user@jakarta.apache.org/msg14601.html
> >
> > This one suggests a workaround which involves precompiling the jsp pages:
> > http://www.mail-archive.com/struts-user@jakarta.apache.org/msg12335.html
> >
> > This one suggests dropping back to tomcat 3.2.1
> > http://www.mail-archive.com/struts-user@jakarta.apache.org/msg12400.html
> >
> >
> > thanks in advance,
> >
> > bill m
