Hi, Very interesting. Thank you for the account. I'm not going to get into a tomcat vs. resin (or vs. other for that matter) debate. My question is: why did you change from Resin to Tomcat?
Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Edgar Dollin [mailto:[EMAIL PROTECTED]] >Sent: Monday, January 20, 2003 2:46 PM >To: '[EMAIL PROTECTED]' >Subject: Caucho Resin to Tomcat Conversion > >I recently completed a cutover of moderately sized app from Resin to Tomcat >and just wanted to put my experiences somewhere for posterity. > >First Resin allows out of order xml documents. Tomcat goes by the book >with >xml. So web.xml, struts-config.xml and any other xml files you have must >but well structured satisfy the DTD. With Resin it is very easy to get >away >from the DTD requirements. > >The second issue is that resin is very creative about the tld's. You can >be >sloppy in both the jsp files and the web.inf about where they are and in >most cases resin will find them. Moving to tomcat you will find any that >are mislocated. If there are tld's inside of jar files, resin finds them >with basic syntax. Tomcat needs the full taglib uri in order to find a tld >inside a jar. > >Resin allows you to mix and match xml formated jsp files with standard >format jsp files. In tomcat you really should stick to one format or the >other. When making your choice which format to use, remember in xml format >you cannot use jsp expressions as attribute values. Also, in tomcat with >the xml format, the assumed page contentType is text/xml, in Resin it is >text/html. Resin allows attribute specification in xml files without >quotes, tomcat does not. Resin allows standard jsp scriptlets inside xml >files, tomcat does not. > >Resin custom tag lifespan is different than Tomcat. Tomcat keeps them >alive >until memory or some other issue forces a release. Resin dumps the custom >tags when the page has completed processing. Keep this in mind if you >share >information between tags, you keep counters in tags, or you have tags that >are instantiated with various numbers of parameters. > >In any event, if you are developing under Resin and want to deploy on some >other container, beware that it lets you do lots of non standard stuff. > >Edgar > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
