Tomcat 4.0
Hi, we are using Tomcat 3.2.4, we deliver to the customer a solution with Tomcat 3.2.4 and we would like to use either Tomcat 3.3 either Tomcat 4.0. Our product work fine with Tomcat 4.0 and Tomcat 3.2.4. Our customers develop their applications using Tomcat 3.2.4 and so it is easy for them to a have a free environment then if they wish they can go to a commercial server. As tomcat 4.0 provides some efficient way to manage log .., compilation JSP, a standard taglib (JSTL) compatible. We are asking ourself if it is a good way to upgrade to Tomcat 4.0 or Tomcat 3.3. Because TC 3.3 is servlet 2.2 and jsp 1.1 compatible, instead Tomcat 4.0 is servlet 2.3 and jsp 1.2 compatible. Most of the commercials products are working today on 2.2 and 1.1 platform so this is why we are asking this? We want to keep a compatibility with S 2.2, JSP 1.1 . If any of you have some responses they are very welcomed. Thomas Colin de Verdière -- SCORT http://www.scort.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat 4.0
Well in fact we would like to use Tomcat 4.0 but our customers may want to use Bea Weblogic, ATG dynamo .. We don't want to force them to use a specific server. My question should be : is there a way in Tomcat 4.0 to make it behave as a servlet 2.2, jsp 1.1 server. I looked at web.xml and there is the path to the dtd which could be constraint to force the customer not to use filter (for example). But for my jsps can i make them specific to a JSP version. Since we are developping demos it could be great to port on any server the customer would like. Am i clear? Michael E. Locasto wrote: Hi, The 2.3/1.2 spec requires implementations to be backward compatible. http://jakarta.apache.org/tomcat/ As required by the specifications, Tomcat 4.0 also supports web applications built for the Servlet 2.2 and JSP 1.1 specifications with no changes. As far as the choice between 3.3.1 and 4.x, people have their favorites. A lot of people run either very happily. There are arguments for both approaches, but I'd say the critical factor for you is how involved your users are in the administration of some Tomcat instance. The decision is yours; I suppose you could offer both environments as development for any of your customers interested in migration. Let them do the assessment for you :) Regards, Michael Locasto - Original Message - From: Thomas Colin de Verdière [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, July 31, 2002 8:48 AM Subject: Tomcat 4.0 Hi, we are using Tomcat 3.2.4, we deliver to the customer a solution with Tomcat 3.2.4 and we would like to use either Tomcat 3.3 either Tomcat 4.0. Our product work fine with Tomcat 4.0 and Tomcat 3.2.4. Our customers develop their applications using Tomcat 3.2.4 and so it is easy for them to a have a free environment then if they wish they can go to a commercial server. As tomcat 4.0 provides some efficient way to manage log .., compilation JSP, a standard taglib (JSTL) compatible. We are asking ourself if it is a good way to upgrade to Tomcat 4.0 or Tomcat 3.3. Because TC 3.3 is servlet 2.2 and jsp 1.1 compatible, instead Tomcat 4.0 is servlet 2.3 and jsp 1.2 compatible. Most of the commercials products are working today on 2.2 and 1.1 platform so this is why we are asking this? We want to keep a compatibility with S 2.2, JSP 1.1 . If any of you have some responses they are very welcomed. Thomas Colin de Verdière -- SCORT http://www.scort.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Thomas Colin de Verdière SCORT http://www.scort.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat 4.0
There are not very involved since they should use another servlet container, even an application server. We have many of our customers using Tomcat 3.2.4 but some use Websphere, other WebLogic ... Our product work on tomcat we have our own Servlets and taglib delivered in WEB-INF/lib/ of our demos applications, we have configuration files in a subdirectory of the conf directory. There are some properties file for jndi access. Our product can be customized. This customization is on the properties file but also on jsps and servlets we deliver. For example we can have the customer can change an init-param for a servlet and he could also want to modify a Jsp page by adding custom tags. This customization the customer can do it anytime. But if he wants to port his customized application to another server we don't want him to use some jsp 1.2 specific features like using JSTL in our jsp since most of products are not jsp 1.2 compatible. The fact is that i want to migrate my taglib to jsp 1.2 compatible and i don't want to write (and support) it for both jsp 1.1 and jsp 1.2 server. We want a smooth migration .. Michael E. Locasto wrote: Hi, The 2.3/1.2 spec requires implementations to be backward compatible. http://jakarta.apache.org/tomcat/ As required by the specifications, Tomcat 4.0 also supports web applications built for the Servlet 2.2 and JSP 1.1 specifications with no changes. As far as the choice between 3.3.1 and 4.x, people have their favorites. A lot of people run either very happily. There are arguments for both approaches, but I'd say the critical factor for you is how involved your users are in the administration of some Tomcat instance. The decision is yours; I suppose you could offer both environments as development for any of your customers interested in migration. Let them do the assessment for you :) Regards, Michael Locasto - Original Message - From: Thomas Colin de Verdière [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, July 31, 2002 8:48 AM Subject: Tomcat 4.0 Hi, we are using Tomcat 3.2.4, we deliver to the customer a solution with Tomcat 3.2.4 and we would like to use either Tomcat 3.3 either Tomcat 4.0. Our product work fine with Tomcat 4.0 and Tomcat 3.2.4. Our customers develop their applications using Tomcat 3.2.4 and so it is easy for them to a have a free environment then if they wish they can go to a commercial server. As tomcat 4.0 provides some efficient way to manage log .., compilation JSP, a standard taglib (JSTL) compatible. We are asking ourself if it is a good way to upgrade to Tomcat 4.0 or Tomcat 3.3. Because TC 3.3 is servlet 2.2 and jsp 1.1 compatible, instead Tomcat 4.0 is servlet 2.3 and jsp 1.2 compatible. Most of the commercials products are working today on 2.2 and 1.1 platform so this is why we are asking this? We want to keep a compatibility with S 2.2, JSP 1.1 . If any of you have some responses they are very welcomed. Thomas Colin de Verdière -- SCORT http://www.scort.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Thomas Colin de Verdière SCORT http://www.scort.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
extends JSP
Hello, is there any constraints in extending a JSP : i use %@ page extends=myjsp % is there any performance issue ? Thanks -- Thomas Colin de Verdière SCORT http://www.scort.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: extends JSP
do you know if there are any constraints except these defined in JSP 8.2.4 Thanks for any help or experience Thomas Colin de Verdière wrote: Hello, is there any constraints in extending a JSP : i use %@ page extends=myjsp % is there any performance issue ? Thanks -- Thomas Colin de Verdière SCORT http://www.scort.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
