Page History

...

We decide to stage the Tuscany/Geronimo integrations based on the discussions on both mailing lists. Here is a summary of the basic ideas.

• Stage 1: Deploy tuscany runtime together with the application artifacts as a JEE web application
  We can start to develop composite applications using SCA programming model to assemble a few components, access existing web services or EJB session beans, expose SCA component services over various protocols such as Web Services, JSONRPC, Feed (ATOM and RSS). The web components such as Servlet, JSP can talk to the SCA aassembly. The SCA assembly can talk to existing services and can provide services for JEE programs to consume.

• Deploy Stage 2: Integrate tuscany runtime as a plugin for Geronimo: tight integration with the bundled containers such as Tomcat, Axis2, ActiveMQ, OpenEJB.
  With this approach, SCA applications can be deployed to Geronimo via the Tuscany plugin. The Geronimo can then manage/run the SCA contributions and composites. The Tuscany plugin also interacts with other containers in the Geronimo assembly such as Tomcat/Jetty, OpenEJB, ActiveMQ to provide various binding support for SCA services. The plugin should integrate with the QoSs such as Transaction and Security provided by Geronimo to support SCA intents/policies.

• will be built on top of Option 2Stage 3: Enable Geronimo JEE to support SCA as implementation types. The main objective to support the SCA JEE integration spec: http://www.osoa.org/download/attachments/1048948/SCA_JAVAEE_integration_v11.doc.
  With the SCA-enabled JEE, the application developers can use both the SCA and JEE programming model. Both SCA and JEE artifacts can participate the assembly and be wired against each other in the SCA domain.

3. Web Application based Tuscany/Geronimo Shadow Integration

...