Hi Raymond/Jay,
I would like to join this effort. I would like to discuss what
is expected of the deep integration. I will just list down my
understanding of both the current and proposed integrations
Understanding of the Current Integration
1) TuscanyContextListener creates an SCA domain when the servlet is
created and then destroys it when the servlet is destroyed.
2) During SCA domain creation it looks up the composites and deploys
them in the domain
Creates a webapp module activator for registering servlet hosts.
3) Finally we have a servlet that forwards requests to the servlet
registered with the Tuscany Servlet Host.
4) An SCADomain is created for each application and we can lookup the
services from the SCADomain.
5) During SCADomain creation a runtime is also created for the DefaultSCADomain.
7) All tuscany classes are loaded repeatedly for each application in
separate classloaders.
8) A runtime is created per application
Understanding/Doubts about the proposed Integration.
1) Each SCA application will have an SCA module which will be a jar
with an SCDL in META-INF. This jar can also be part of an EAR. . There
will be a Tuscany deployer that will take care of deploying the SCA
modules. Should WAR files be also able to contain SCA jars?
2) Each App will have an SCA Domain which will be instantiated when
the application starts. Is this assumption correct or can there be
multiple SCADomains per app?
3) The Tuscany classes are loaded only once and then shared between
the different SCA applications.
4) There will be multiple domains instantiated from different
applications and there should be a server wide domain registry where
applications can look up and invoke different composites from domains
different from their own. (Can this be Global JNDI/Gbean refs or is
there something specific in tuscany).
5) There should be only a single Tuscany Runtime for the entire
geronimo instance.
6) How can we lookup the services running in one geronimo instance
from an app in another geronimo instance. Is this supported in Tuscany
These are just the initial set of points/questions that hit me when I
thought about the integration. Jay /Raymond I guess you guys will be
aware of many other points as well. Can you reply with your analysis
so that we can flesh out the requirements completely in the mailing
list. That way both the communities can contribute their thoughts. If
you have already started can you just point me to where I can catch up
on what has happened?
Thanks
Manu
On 4/26/07, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi, Geronimo community.
As you may know, Tuscany is an Apache project under incubation to provide an
open source SOA infrastructure. For more information, you can visit
http://cwiki.apache.org/TUSCANY/.
Tuscany implements the SCA specification (http://www.osoa.org) and allows
you to develop and run SCA components in various hosting environments. We
currently integrate with Tomcat and Jetty and would like to try to integrate
with Geronimo as well. I would like to start some discussions here to figure
out the best way to do that.
After some preliminary investigations of Geronimo, I feel that there are two
options on the table so far.
1) Shallow integration: Package SCA applications together with the Tuscany
runtime as WARs and deploy them Geronimo as Web applications. It's basically
the integration with a Web container. We register a TuscanyContextListner
(which implements javax.servlet.ServletContextListener) in web.xml to
start/stop the Tuscany runtime when the web application is started/stopped.
This will allow us to support the following use cases:
* A Web application hosted by Geronimo with business logic written as SCA
components
* Expose one or more SCA components as Web services over HTTP as supported
by the Web container.
2) Deep integration: We package the Tuscany runtime and its dependencies as
Geronimo modules and deploy them to Geronimo (which is similar to how Tomcat
is integrated as the Web container for Geronimo). We can then create a
Tuscany plugin (a collection of modules) so that it can be added to
Geronimo. The Tuscany container will then handle SCA-specific deployment
plans to install SCA applications and provide runtime infrastructure for
them.
On top of Option 2, we could further integrate Geronimo's J2EE capabilities
such as EJB, WS, JMS and JCA with Tuscany. Basically, SCA components will be
able to access JEE services (using SCA composite references) and SCA
components will be able to expose services (SCA composite services) over JEE
protocols as well.
This will allow us to support the following use cases:
* Any J2EE application hosted by Geronimo would be able to take advantage of
SCA programming model
* Provide SCA services over various protocols such as RMI/IIOP, JMS and JCA
* Invoke existing JEE applications (EJB, JMS backend, JCA-based EIS or Web
Services) from SCA components
Any thoughts?
Thanks,
Raymond
Apache Tuscany committer
