You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

A page to capture the ideas and discussions on Geronimo-Tuscany Integration. This wiki page is a summary of the discussions on the mailing lists. Feel free to help in developing the ideas here.

Use Cases

Currently we are considering three use cases. These are just the initial set and they may be changed or more added as we go forward. The use cases are listed below

  1. I develop SCA components, assemble them in a composite, package them
    in an SCA contribution. I don't really know what a WAR or an EAR is, I'm
    just using the SCA programming model and packaging model. I deploy my
    SCA contribution to Geronimo and run it there. I can then access these services using
    the various bindings that Tuscany provides.
  2. I'm assembling SCA components, some of them developed using the SCA
    programming model (Java components, BPEL components or composite
    components for example) and I want to re-use an EJB module in my
    assembly, allowing other SCA components to talk to its session beans
    using the SCA programming model. That EJB module does not know anything
    about SCA, it only uses the EJB programming model.
  3. I want to use a Web app in my SCA assembly and call SCA components
    from it. I should be able to declare an SCA component representing my
    Web app, wire that component to other SCA components in the assembly,
    and then magically the wired references will be available as proxies for
    use in my JSPs, allowing me to call an SCA component using a simple
    jsp:useBean tag. I should also be able to access the services inside of my
    servlets, filters, etc by using annotations.

For achieving #1 (the first level of integration) we need to consider the following points.

  1. Tuscany modules should be deployable in Apache Geronimo.
    For this we need to write a geronimo-plugin with a deployer that can handle tuscany modules.
    On how to write a geronimo-plugin please refer the link below.
    http://cwiki.apache.org/GMOxDOC11/advanced-plugin-sample.html
  2. Tuscany modules should use the existing geronimo http and web-service infrastructure.
    Geronimo provides both Tomcat and Jetty as web containers. They should be used for all incoming and
    outgoing http requests. This can be achieved by writing a custom class that implements the
    org.apache.tuscany.sca.http.ServletHost interface and registering it in the extension point registry.
    Geronimo also provides both axis2 and cxf as web service containers. These should be used instead of
    separate instances.

Initially this is what we will be trying to achieve. There are two mail chains providing more info

http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg17077.html http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg19277.html http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg19424.html

  • No labels