This is used to control if the Tuscany runtime classes are shared by
multiple applications from the classloading perspective. Sharing the classes
doesn't prevent the nodes from being part of different SCA domains. On the
other hand, web applications that don't share the Tuscany classes can join
the same SCA domain too.
Unmarking the "share" flag allows each web application has its own instances
of the Tuscany classes. It's the pretty much the same as packaging all the
Tuscany jars in the web application. This option removes the duplication of
Tuscany jars and the requirement of setting up the web.xml.
Basically, there are three options:
1) Multiple web applications share the same Tuscany classes
2) Multiple web applications load their own instances of Tuscany classes
from the same physical location
3) Each web application loads their own instances of Tuscany classes from
their own Tuscany jars
Thanks,
Raymond
--------------------------------------------------
From: "ant elder" <[email protected]>
Sent: Monday, June 15, 2009 3:20 AM
To: <[email protected]>
Subject: Re: svn commit: r779778 - in /tuscany/java/sca/distribution/tomcat:
tomcat-hook/src/main/java/org/apache/tuscany/sca/tomcat/
tomcat-servlet/src/main/java/org/apache/tuscany/sca/war/
tomcat-war/src/main/webapp/
On Thu, May 28, 2009 at 10:24 PM, <[email protected]> wrote:
Author: rfeng
Date: Thu May 28 21:24:41 2009
New Revision: 779778
URL: http://svn.apache.org/viewvc?rev=779778&view=rev
Log:
Add a checkbox on the jsp to configure if Tuscany is shared or isolated
by the webapps
What is the use case for this? I'm wondering if we need it now that
there is a domain shared across the Tomcat instance so those need to
share Tuscany and we've now support for webapps to embed their own
copy of Tuscany when they don't want to shared the server version.
...ant
