You could have both tomcats running in the same server, one for legacy apps and another for new stuff, using mod_jk. It works very well.
-----Mensagem original----- De: Jonathan Mast [mailto:[EMAIL PROTECTED] Enviada em: quarta-feira, 26 de março de 2008 13:14 Para: Tomcat Users List Assunto: Re: Java 1.4.2 to 1.5 upgrade tips What I'm worried about is the Servlet spec. We have some legacy stuff that only compiles correctly using the "servlet.jar" which includes JSP 1.1 I think. Anyways, my fear is that this might not be supported with Java 1.5, and that stuff will have to be recoded to make use of "servlet-api.jar" which would require a lot of work. Any ideas? On Tue, Mar 25, 2008 at 12:39 PM, David kerber <[EMAIL PROTECTED]> wrote: > Jonathan Mast wrote: > > It looks like we might have to upgrade to Java 1.5 from 1.4.2 and I > > was wondering if someone could point me to a guide on the pitfalls > > to watch > out > > for as per Tomcat 5.5. > > > > thanks, > > > > > I don't have a specific reference, but IIRC, there was very little > code that would work correctly in 1.4 and not 1.5. The biggest effort > was finding stuff that could be much more efficiently rewritten in 1.5 > to take advantage of new features. However, even if you don't change > a single line, 1.5 will still likely give you better performance than 1.4.2. > > D > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, > e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
