Matthew Peters wrote:
As you'll guess from the post on Websphere and Tuscany that I put up a
couple of days ago,
My response: http://marc.info/?l=tuscany-user&m=119223827124704
I would like to see where you want to go in the area
of
- Webapp and EJB module integration
I'd like to track the OASIS work on this and implement it in parallel in
Tuscany. Many users have existing J2EE EJB and EAR modules that they'll
need to integrate in bigger SCA compositions. Also Webapp developers
will need a non-intrusive way to wire a Webapp with other SCA components
in an SCA domain.
For example when you wire a webapp to an SCA component, how is the SCA
domain found,
I think that an SCA-enabled runtime (a JEE runtime or any other form of
SCA enabled runtime) needs to be configured with a domain URI that it
will belong to.
At the moment in Tuscany we just pass that URI when we bootstrap the
runtime. If you're up for a long read, see the SCA Domain discussion
thread on the tuscany-dev list, here's a pointer to the last email in
that thread: http://marc.info/?l=tuscany-dev&m=119196408721454&w=2
and who starts and stops it?
The domain administrator :) independent of what JEE or other apps are
deployed to it.
How and when did the components
get deployed into it?
I can think of three main scenarios:
- An SCA domain administrator goes to his domain management application
and uploads a contribution, then adds some composites from the
contribution to the domain level composite. At that point the SCA domain
management app finds the appropriate runtime node for the contribution,
distributes the contribution to the node.
- An administrator goes to a node belonging to an SCA domain, uploads a
contribution, then adds some composites from the contribution to the
domain level composite.
- A contribution and composites have already been installed on a node by
some mechanisms unknown to Tuscany, the SCA domain administrator goes to
the domain management application to register the presence of these
composites in the domain.
... and all kinds of variations of the above, but these scenarios are
not really specific to JEE integration, it's just how I view an SCA
domain being used.
And wre we ever going to have webapps which *are*
SCA components so that we want to do dependency injection directly into a
servlet for example?
I guess this is the idea of being able to declare a JEE Web module as an
SCA component implementation. You can declare SCA references on the Web
module, wire them to SCA services, and invoke them from code running in
the Webapp.
I'm not very fond of mixing programming models, as it makes tech people
happy but usually gets in the way of the business application developer
who's trying to achieve something without having to learn 4 programming
languages, 12 APIs, and 37 different ways to bind XML to Java. So I hope
we can do this in a non-intrusive way without introducing too many SCA
programming model artifacts in the JEE Webapp.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
