Hi,
I view the WAR (a single web module) is a simplified deployment of EAR
(might contain multiple modules). I meant to say that we can embed SCA
assembly in a JEE application, for example, a bunch of java components wired
together to provide some services to the EJB, JSP or Servlet. It's probably
related to the "Use Recursive SCA Assembly in Enterprise Applications"
scenario in [1]. I guess it's the degenerated case of the
META-INF/application.composite without the capability of
<implementation.ejb> or <implementation.web>.
[1] http://www.osoa.org:80/pages/viewpage.action?pageId=3980
Thanks,
Raymond
----- Original Message -----
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, January 23, 2008 9:57 AM
Subject: Re: SCA contribution packaging schemes: was: SCA runtimes
Raymond Feng wrote:
A & B seem to be the two primary schemes. A variation of option A is that
we package all the jars (as utility jars) into an EAR so that JEE
applications can use Tuscany/SCA.
Can you help me understand what you meant by: "so that JEE applications
can use Tuscany/SCA"?
Are you talking about the "SCA assembly of JEE applications" described in
http://www.osoa.org/pages/viewpage.action?pageId=3980 using something like
META-INF/application.composite?
--
Jean-Sebastien
---------------------------------------------------------------------
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]
