ant elder wrote:
On Thu, Jul 3, 2008 at 11:43 AM, ant elder <[EMAIL PROTECTED]> wrote:
On Tue, Jul 1, 2008 at 12:57 AM, Raymond Feng <[EMAIL PROTECTED]> wrote:
I suggest that we use a usage scenario-driven approach to create a list of
tasks/features and mark them either it's common to SCA independent of the
hosting environment or it's specific to Geronimo.
Here is a few roles a Geronimo instance can play in the SCA domain:
1) Geronimo is a member of a SCA domain to deploy/run SCA applications
2) Geronimo hosts the SCA domain admin application
3) Geronimo hosts (some) contributions for a SCA domain
Now that the 1.0 version of the SCA JEE spec [1] is out that defines
several concrete use cases and scenarios we can use to define the tasks and
features we need. For example, how about one goal be running in Geronimo the
application.ear shown at line 1131 page 41 "Appendix A – use cases" of the
SCA JEE spec.
[1]
http://www.osoa.org/download/attachments/35/SCA_JAVAEE_Integration_V100.pdf
Any comments on this or does silence mean that example from the JEE spec is
an ok use case to be working towards for our first try at the new Geronimo
integration?
I think the use cases suggested by Raymond and the use cases in Appendix
A of the SCA Java EE spec suggested by you are all excellent starting
points to validate Tuscany integration with Geronimo. It seems the roles
Raymond suggests are larger in scope and might touch more bindings and
data bindings than more specific Java EE integration.
--
Thanks, Dan Becker
