Currently we are trying to create community edition for our framework to run at TC 7, what we truly need is: user can deploy a app as a shared library in runtime, and other deployed apps can access it and get its own stack and would not interfere each other. This is basic features found in WLS and WAS,
>From all inputs so far I get, look like TC7 does not give user a choice to >deploy their app as a shared library or a normal app, but a normal app, right? > From: chuck.caldar...@unisys.com > To: users@tomcat.apache.org > Date: Fri, 22 Apr 2011 13:27:01 -0500 > Subject: RE: shared library in tomcat container runtime` > > > From: Yongqin Xu [mailto:yong...@hotmail.com] > > Subject: RE: shared library in tomcat container runtime` > > > for our own shared lib jars, we have to duplicate them for each > > deployed apps, even if sometimes the shared lib jars could be > > over 100MB. That would really cumbersome! > > Not really; just have your automated script include them when it creates your > .war files. (That part of the distribution process is automated, isn't it? > If not, why not?) The amount of excess storage consumed is a trivial expense > these days, and you will save yourself an incredible amount of grief by not > having to deal with versioning synchronization when updating the libraries > and webapps. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you received > this in error, please contact the sender and delete the e-mail and its > attachments from all computers. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
