Re: Many hosts sharing servlets

[Bill Sutton]

Thanks for your quick reply. Yes I have read the pros & cons and I would 
prefer not to use the invoker but the work in updating many webapps each 
time a servlet changes is daunting, particularly using Plesk.

Bill
----- Original Message ----- 
From: "QM" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Sent: Wednesday, April 20, 2005 8:48 PM
Subject: Re: Many hosts sharing servlets


On Wed, Apr 20, 2005 at 05:06:00PM +1000, Bill Sutton wrote:
: I have 100+ servlets and classes that I want to be available to up to 
100
: virtual hosts.

: So I have tried to put all the classes into /var/tomcat4/shared/classes.
: In each host, I deploy a servlets.war file that contains only the 
following
: [snip: web.xml with Invoker servlet]
: Questions
: Is there a better way to do this ?

"Better" depends on your goals, but most a lot of people would say that
using the invoker has its pros and cons.  Mostly cons. =) (See the
archives for why.)
You could just JAR up the 100+ servlet classes and drop them in each
webapp's WEB-INF/lib.  Next, write something to create a set of proper
<servlet/> and <servlet-mapping/> entries for those servlets.  This is a
one-time hit that will pay off long-term.
: Will tomcat be using hugely more memory than jserv was ?
Depends on your app.  Only a load test + profiling will let you know.
-QM
--
software   -- http://www.brandxdev.net/
tech news  -- http://www.RoarNetworX.com/
code scan  -- http://www.JxRef.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]