Return-Path: Delivered-To: apmail-ws-tuscany-dev-archive@locus.apache.org Received: (qmail 53949 invoked from network); 3 Jan 2008 00:13:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Jan 2008 00:13:05 -0000 Received: (qmail 19762 invoked by uid 500); 3 Jan 2008 00:12:53 -0000 Delivered-To: apmail-ws-tuscany-dev-archive@ws.apache.org Received: (qmail 19454 invoked by uid 500); 3 Jan 2008 00:12:53 -0000 Mailing-List: contact tuscany-dev-help@ws.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: tuscany-dev@ws.apache.org Delivered-To: mailing list tuscany-dev@ws.apache.org Received: (qmail 19445 invoked by uid 99); 3 Jan 2008 00:12:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jan 2008 16:12:53 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [76.96.62.40] (HELO QMTA04.westchester.pa.mail.comcast.net) (76.96.62.40) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jan 2008 00:12:41 +0000 Received: from OMTA13.westchester.pa.mail.comcast.net ([76.96.62.52]) by QMTA04.westchester.pa.mail.comcast.net with comcast id YHTu1Y00617dt5G050kX00; Thu, 03 Jan 2008 00:12:32 +0000 Received: from delfinoj60.burlingame.ibm.com ([32.97.110.142]) by OMTA13.westchester.pa.mail.comcast.net with comcast id YQCS1Y00K34NxMc3Z00000; Thu, 03 Jan 2008 00:12:28 +0000 X-Authority-Analysis: v=1.0 c=1 a=1Y2t2h20yfwA:10 a=eq7umQVVXD4VYO39IzsA:9 a=SbvqV3aJYz9uxQZ8Xa0A:7 a=prh--Vi96Ffj6eNEx9LXymALtQgA:4 a=QJAqVYndk0IA:10 Message-ID: <477C287E.6080802@apache.org> Date: Wed, 02 Jan 2008 16:12:46 -0800 From: Jean-Sebastien Delfino User-Agent: Thunderbird 2.0.0.9 (X11/20071031) MIME-Version: 1.0 To: tuscany-dev@ws.apache.org Subject: Re: Using contributions in the tutorial, was: Improving the store tutorial module structure References: <4761D396.2070908@apache.org> <4762A137.3040504@gmail.com> <4762FF97.7050200@apache.org> <4769A1F6.7030504@apache.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Rajini Sivaram wrote: > Sebastien, > > When I was implementing OSGi bundle contributions, I was very frustrated > about the fact that even though bundles can have cyclic dependencies, > bundles with cyclic dependencies could not be added to SCA, if the bundles > contained SCA artifacts (composites/componentType files). OSGi copes with > cyclic dependencies because bundles have separate install and start methods. > So classes need to get resolved only before the start method is called. The > bundle is moved to resolved state by the OSGi runtime when its dependencies > are satisfied, and only resolved bundles can be started. With SCA > contributions, when would the composites/componentType files in a > contribution get processed, if it is not done when the contribution is > added? Class resolution for contributions is lazy, and hence the ordering of > contributions is only relevant when there are multiple contributions > containing the same class. But classes used in SCA composites and > componentType files get resolved when those files are processed, and at the > moment addContribution is the trigger, requiring all dependent contributions > containing classes referred to in composites/componentType files to be > installed first. If addContribution is not the trigger to process > composites, I am not sure what the trigger would be. node.start() for the > node? What about the domain? Wouldn't it have been much simpler if Tuscany > had a better lifecycle layer (like OSGi :-))? > > > > Thank you... > > Regards, > > Rajini > Short answer to a long question :) when a composite is assigned to a node: node.setComposite(composite). -- Jean-Sebastien --------------------------------------------------------------------- To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org For additional commands, e-mail: tuscany-dev-help@ws.apache.org