Simon Laws wrote:
[snip]
If I understand this correctly it looks like a reasonable way to extend the
Fruit&Veg scenario. In the current scenario I believe that the catalog
services, when run from the "cloud" module are running as part of the
distributed domain but rely on the embedded Jetty support .
Correct
So let me
confirm that you are suggesting three new things
1. creating implementation.ejb to support the Vegetable catalog
2. choosing a different hosting option in order to deploy SCA applications
to a Geronimo server such that they take part in the SCA domain
3. choosing a different hosting option in order to deploy SCA applications
to a Tomcat server such that they take part in the SCA domain
Yes to 1 and 3.
With (2), the vegetable catalog is an existing JEE application. So we're
not going to deploy it to Geronimo as a new SCA contribution/application
etc, it is already there running on Geronimo, and the point of the
merger is to not have to rewrite it in SCA form, but instead model its
presence in the domain with an SCA composite, then wire to it.
At the moment I'm in the middle of the domain enhancements to tidy the
service discovery mechanisms we have already discussed but am keen to help
get this up and running when I'm done (hopefully I'll finish by current
changes today).
Great!
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
