You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by gaurav <ga...@hclcomnet.co.in> on 2005/06/08 12:48:30 UTC
Jserv to Tomcat migration
Hi List,
We thinking migrating some legacy code from Jserv 1.1.2 to
tomcat 5.
We some running a legacy application that runs entirely on servlet
I am looking around some practical insightful tips/ guidance on this
matter ...it there is any Jserv to Tomcat migration guide book or any
other documentation which I can refer to or if any one ever faced
some problems then pl share with me :-)
Regards,
GP
**********************************************************************
/pl ignore anything below this ;-)/
************************************************************************
DISCLAIMER:
This e-mail contains confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure, use or distribution of the material in this e-mail is strictly forbidden.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Jserv to Tomcat migration
Posted by QM <qm...@brandxdev.net>.
On Wed, Jun 08, 2005 at 04:18:30PM +0530, gaurav wrote:
: We thinking migrating some legacy code from Jserv 1.1.2 to
: tomcat 5.
: I am looking around some practical insightful tips/ guidance on this
: matter ...it there is any Jserv to Tomcat migration guide book or any
: other documentation which I can refer to or if any one ever faced
: some problems then pl share with me :-)
The process is the same for migrating between any two servlet
containers:
1/ make note of any vendor-specific hooks you use in your current app.
Don't expect them to be in the other container. Rewrite your app to
work without them.
2/ Review the servlet spec that fits the destination container (v2.4 for
Tomcat 5). If it's not the same servlet spec version as your current
container, make note of any deprecations (such as SingleThreadModel) or
other changes. Code your app to work per the spec.
3/ Note how the new container provides services (such as database
pooling).
That's about it. =)
All jokes aside, the point of the spec is that 100% spec-compliant apps
should be able to migrate between spec-compliant containers without much
hassle. If you've stuck to the spec this whole time, your migration
shouldn't be a problem.
-QM
--
software -- http://www.brandxdev.net/
tech news -- http://www.RoarNetworX.com/
code scan -- http://www.JxRef.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org