1) Disk is cheap.
2) Build scripts can easily push the common code out to all your apps in
a reproducable manner.
3) Seperate code makes regression upgrades easier to do since there is
always that one app which cant be upgraded
While you may be "sharing code" - all the code will be living in
different classloaders (one per webapp) so at most - you are saving disk.
-Tim
Richard Sayre wrote:
Is it possible to have several contexts pointing to the same code
base? If I am hosing an application and other clients would like to
use it, is it possible to set them up a seprate context that points to
one set of JSP/Java Classes?
Are there disadvantages in doing this?
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
