Return-Path: Delivered-To: apmail-tuscany-dev-archive@www.apache.org Received: (qmail 48888 invoked from network); 3 Jul 2008 10:43:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Jul 2008 10:43:54 -0000 Received: (qmail 23745 invoked by uid 500); 3 Jul 2008 10:43:54 -0000 Delivered-To: apmail-tuscany-dev-archive@tuscany.apache.org Received: (qmail 23714 invoked by uid 500); 3 Jul 2008 10:43:54 -0000 Mailing-List: contact dev-help@tuscany.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tuscany.apache.org Delivered-To: mailing list dev@tuscany.apache.org Received: (qmail 23703 invoked by uid 99); 3 Jul 2008 10:43:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2008 03:43:53 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ant.elder@gmail.com designates 64.233.182.191 as permitted sender) Received: from [64.233.182.191] (HELO nf-out-0910.google.com) (64.233.182.191) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2008 10:43:00 +0000 Received: by nf-out-0910.google.com with SMTP id g16so214086nfd.38 for ; Thu, 03 Jul 2008 03:43:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:in-reply-to:mime-version:content-type:references; bh=eCboZZBANAS1MUH+tT9wVGJ7UIJGxAe3Cil5p81WMOg=; b=tfKEo3qluqij5gq72we9aMl0oIVlgyh60goU0DgxcKW66VSsmE2Kpyo+mQSJAX23Rg mv1+tK7rx5yLB8zG/G6ay0C21KZPjPTKSm59E3prkdSckbb/ipdwaxeFZRduEsAjQdPV Y2Vq/BpnylxEX0YQCFZc1qlZuiUsdFi/sif+E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:in-reply-to:mime-version :content-type:references; b=ScQE1Gu94MRmIWQB6WcHy/ugMA87jDlvKonOAJPcMv8t3/d39eTQbJlM/rlwOlekEr fo8FfVXNM0cO/HQaP9SFJrhYaO/wXfPRvrcNGbk3kHoRuRNArZYacEs+GqBBD9X0X+4V WoHfxK9NoNj3H5cV5g9k7cqbn2H3+8GfCir1s= Received: by 10.210.110.5 with SMTP id i5mr3404262ebc.18.1215081800431; Thu, 03 Jul 2008 03:43:20 -0700 (PDT) Received: by 10.210.52.3 with HTTP; Thu, 3 Jul 2008 03:43:20 -0700 (PDT) Message-ID: <71e1b5740807030343n714611a2la1539d96ac4ba7e3@mail.gmail.com> Date: Thu, 3 Jul 2008 11:43:20 +0100 From: "ant elder" Reply-To: antelder@apache.org To: dev@tuscany.apache.org Subject: Re: Tuscany integration with Geronimo: What's common to SCA and what's sepcific to Geronimo?, was: Re: GSoC Project - Tuscany SCA support in the Geronimo admin Console In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2911_21473336.1215081800418" References: <930503ab0804290608p2a8cca90v49c91c4a61f71ad@mail.gmail.com> <5a75db780804290835r2d2b8ffch8d63384448dcfa7d@mail.gmail.com> <930503ab0804300633n51e386e4t69d2f1951f5ea904@mail.gmail.com> <930503ab0805052251p2a907a3dy4c7207fa9e8ef474@mail.gmail.com> <930503ab0805280108o253b4c1dme58222caf6e44a53@mail.gmail.com> <5a75db780805280719o6aea08d7w62245b07b5070347@mail.gmail.com> <930503ab0806070013i6774e13s2a73396e840ac869@mail.gmail.com> <485A5FB3.8070705@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_2911_21473336.1215081800418 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, Jul 1, 2008 at 12:57 AM, Raymond Feng wrote: > Hi, > > I would like to extend the discussion a bit to help us better understand > what user experience we would like to bring to Geronimo developers/users > with Tuscany/SCA. > > I suggest that we use a usage scenario-driven approach to create a list o= f > 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 > > * Connect to the SCA domain admin app to get the image of a resolved > composite application > * Be able to deploy the resolved composite application in the VM of > Geronimo, either as JEE application or standalone [Specific to Geronimo] > * Run the resolved composite application > * Provide the binding/implementation/policy extensions to realize SCA > binding/implementation/policy types.[[Specific to Geronimo] > * Hook with the other containers in Geronimo to provide various binding= s, > such as HTTP connectors with Tomcat > * Hook with the QoSs such Transaction and Security provided by Geronimo > to implement the SCA policies > * Create/manage related resources for some bindings, such as JMS connecti= on > factories and queues [Specific to Geronimo] > > 2) Geronimo hosts the SCA domain admin application > > * Manage the configuration (Contributions/Composites/Nodes) for a SCA > domain [Common to SCA] > * Resolve the wirings at SCA domain level for the top-level composites > [Common to SCA] > * Deploy the resolved composite image to a in-process or remote host [A > Geronimo or JSR88 Deployer may be specific to Geronimo] > > 3) Geronimo hosts (some) contributions for a SCA domain > * Expose them as URLs to the SCA domain admin application. In this case, = It > functions as a repo for SCA contributions. [Specific to Geronimo] > > I think we should only try to implement a feature in a geronimo-specific > way only if it's specific to Geronimo. > > Thanks, > Raymond > > > Now that the 1.0 version of the SCA JEE spec [1] is out that defines severa= l concrete use cases and scenarios we can use to define the tasks and feature= s we need. For example, how about one goal be running in Geronimo the application.ear shown at line 1131 page 41 "Appendix A =96 use cases" of th= e SCA JEE spec. ...ant [1] http://www.osoa.org/download/attachments/35/SCA_JAVAEE_Integration_V100.pdf ------=_Part_2911_21473336.1215081800418 Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

On Tue, Jul 1, 2008 at 12:57 AM, Raymond= Feng <enjoyjav= a@gmail.com> wrote:
Hi,

I would like to extend the discussion a bit to help us better understand wh= at user experience we would like to bring to Geronimo developers/users with= Tuscany/SCA.

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 t= he 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

* Connect to the SCA domain admin app to get the image of a resolved compos= ite application
* Be able to deploy the resolved composite application in the VM of Geronim= o, either as JEE application or standalone [Specific to Geronimo]
* Run the resolved composite application
* Provide the binding/implementation/policy extensions to realize SCA bindi= ng/implementation/policy types.[[Specific to Geronimo]
  * Hook with the other containers in Geronimo to provide various bin= dings, such as HTTP connectors with Tomcat
  * Hook with the QoSs such Transaction and Security provided by Gero= nimo to implement the SCA policies
* Create/manage related resources for some bindings, such as JMS connection= factories and queues [Specific to Geronimo]

2) Geronimo hosts the SCA domain admin application

* Manage the configuration (Contributions/Composites/Nodes) for a SCA domai= n [Common to SCA]
* Resolve the wirings at SCA domain level for the top-level composites [Com= mon to SCA]
* Deploy the resolved composite image to a in-process or remote host [A Ger= onimo or JSR88 Deployer may be specific to Geronimo]

3) Geronimo hosts (some) contributions for a SCA domain
* Expose them as URLs to the SCA domain admin application. In this case, It= functions as a repo for SCA contributions. [Specific to Geronimo]

I think we should only try to implement a feature in a geronimo-specific wa= y only if it's specific to Geronimo.

Thanks,
Raymond



Now that the 1.0 version of the SCA JEE spec= [1] is out that defines several concrete use cases and scenarios we can us= e 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 &quo= t;Appendix A =96 use cases" of the SCA JEE spec.

   ...ant

[1] http://www.osoa.org/downlo= ad/attachments/35/SCA_JAVAEE_Integration_V100.pdf
------=_Part_2911_21473336.1215081800418--