Return-Path: Delivered-To: apmail-tuscany-dev-archive@www.apache.org Received: (qmail 57617 invoked from network); 1 Oct 2009 07:51:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Oct 2009 07:51:13 -0000 Received: (qmail 22155 invoked by uid 500); 1 Oct 2009 07:51:13 -0000 Delivered-To: apmail-tuscany-dev-archive@tuscany.apache.org Received: (qmail 22076 invoked by uid 500); 1 Oct 2009 07:51:13 -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 22068 invoked by uid 99); 1 Oct 2009 07:51:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2009 07:51:13 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ant.elder@gmail.com designates 209.85.218.216 as permitted sender) Received: from [209.85.218.216] (HELO mail-bw0-f216.google.com) (209.85.218.216) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2009 07:51:03 +0000 Received: by bwz12 with SMTP id 12so5429801bwz.20 for ; Thu, 01 Oct 2009 00:49:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=TjEzdx8vuk/i3Rfl4aaA3/dA3fMhQU4e5utOxxqOTIU=; b=X80MpkTrYR79DfnwdVWJcifCaswnnDOnZ+2BPrGoNNdL5bFdp5LvfO5NDsoubuqZgo UtNvsHoNL+/ReBjfvGhUXPpIPwnnZVSi0XM+0dPJ3XlP0ACgyRJYfGo3OTAyLDCEuq+G swg9TAb7UZyM1GULOXVejN53gjSlUaaY//D8o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=TypzcsE/t5QG2bddVmw9j3UgovC31TEGYb2yGtyAvoFWaYZP0p8q6v2hP9qsolpRGF vFi/KwiKv4slVeyWy6XiVYVg0Rwkp2KqpxPb5TLMVddJQJBV+Y2oZ06O80ChCCDW+leT URACw983TLDHizxwrD93MRB6x6oy2gHm5Oy8g= MIME-Version: 1.0 Received: by 10.204.162.137 with SMTP id v9mr685831bkx.60.1254383383437; Thu, 01 Oct 2009 00:49:43 -0700 (PDT) Reply-To: antelder@apache.org In-Reply-To: References: Date: Thu, 1 Oct 2009 08:49:43 +0100 Message-ID: <71e1b5740910010049j3af076f5ld1254d20ebf693fd@mail.gmail.com> Subject: Re: [2.x] reviewing/summarizing domain operation - was: Re: Discovery-based SCA Domain for OSGi RFC 119 From: ant elder To: dev@tuscany.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Sep 30, 2009 at 11:37 AM, Simon Laws wrote: > b3/ one or more composite files but which are present in > META-INF/sca-deployables (is this still supported?) > No, i think i took out support for that earlier on in 2.x when porting from 1.x, there may be a ML thread. Something like that still seems like a good idea to me though to make it seem easy to create a simple contribution. I'd quite like the spec people to extend the application composite concept in the JEE spec to the Assembly spec so you can have something like application composite with a standard name in a regular contribution like you can have a web.composite in a .war contribution. I guess we could add support for that to Tuscany and see what the spec people think of it? ...ant