Return-Path: Delivered-To: apmail-felix-dev-archive@www.apache.org Received: (qmail 48729 invoked from network); 2 May 2008 18:23:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 May 2008 18:23:15 -0000 Received: (qmail 39752 invoked by uid 500); 2 May 2008 18:23:15 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 39707 invoked by uid 500); 2 May 2008 18:23:15 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 39696 invoked by uid 99); 2 May 2008 18:23:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 May 2008 11:23:15 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of adreghiciu@gmail.com designates 64.233.184.234 as permitted sender) Received: from [64.233.184.234] (HELO wr-out-0506.google.com) (64.233.184.234) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 May 2008 18:22:29 +0000 Received: by wr-out-0506.google.com with SMTP id 76so1123244wra.10 for ; Fri, 02 May 2008 11:22:43 -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:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=KLTJX+ubPHmYqEIpW0NX2WtHj9gCDIh76HavzUIfsHM=; b=liyRS1EjS0xjGr3J4+BGB7ZOzym8x8sd3Nsd51oVcneeA+Ip77/+Cat6fGf7sa8XAqXAwsPF0tQANgkVFglJEy6yhwjJf4E/99ETny+usc5cTZcGvs7ifFtp9SEjrrVVXDYu/8+0JiPIBLT0G+n+qkYW8BwMnjpU1tYGgYcDI3Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=k9DI4f8hseIdFxszNSfJljHklgT2DtTI0KBU6UdS37edvxf0O+EKnXnfh5qntrUe8ZQ9coxlqtnfeQmLfLZhmJo43qkRpGJMH7sEGUE/AJ+hm9/0C3NnFzmW33qTSeM5RO2XNsXvsAksQVva46yBf8xIcrJ6XHKfAYyc2Mv8hk8= Received: by 10.141.141.3 with SMTP id t3mr1484746rvn.52.1209752562245; Fri, 02 May 2008 11:22:42 -0700 (PDT) Received: by 10.141.48.16 with HTTP; Fri, 2 May 2008 11:22:42 -0700 (PDT) Message-ID: <87eb8aee0805021122m5664ca95s8e9032a4b7ba831e@mail.gmail.com> Date: Fri, 2 May 2008 20:22:42 +0200 From: "Alin Dreghiciu" To: dev@felix.apache.org Subject: Re: SpringSource Bundle Repository In-Reply-To: <481B56F3.3040900@ungoverned.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4819FE63.7020303@ungoverned.org> <87eb8aee0805012355x43907cpfc2add1544d994bf@mail.gmail.com> <481B56F3.3040900@ungoverned.org> X-Virus-Checked: Checked by ClamAV on apache.org >From Rob's blog: "The Platform introduces two new mechanisms for referring to third-party dependencies: Import-Bundle and Import-Libary. Import-Bundle is analogous to Require-Bundle except it prevents split packages and the other problems with Require-Bundle. Import-Library provides a mechanism to refer to all the packages exported by a group of bundles" What's also new is: "The PAR format is the recommended approach for packaging and deploying applications for the Platform. A PAR is simply a collection of OSGi bundles (modules) grouped together in a standard JAR file, along with a name and a version that uniquely identify the application. The PAR file is deployed as a single unit into the Platform. The Platform will extract all the modules from the PAR and install them. Third-party dependencies will be installed on-the-fly as needed. The PAR format has three main benefits over deploying the bundles directly into the Platform. Firstly, it's just easier. An average-sized enterprise application might contain 12+ bundles - deploying these by hand will be far too cumbersome. Secondly, the PAR file forms an explicit scope around all the bundles in the application which prevents applications that use overlapping types or services from clashing with each other. This scope is also used by some advanced features such as load-time weaving to ensure that weaving of one application doesn't interfere with weaving of another. Lastly, the PAR forms a logical grouping to define what modules are part of an application and what third-party dependencies the application has. This grouping is used by the management tools to provide a detailed view of the application." Alin On Fri, May 2, 2008 at 8:01 PM, Richard S. Hall wrote: > I think there could be another issue, which I wasn't aware of initially, in > that they introduce some new manifest headers for specifying dependencies. > If they do this for their repository bundles, then it might not be so useful > for us...I am not sure what it means for us, so it will have to be > investigated too. > > -> richard > > > > > Alin Dreghiciu wrote: > > > As I saw, but I did not go to much n detail, the Spring Bundle > > Repository is their own bundle repository, meaning that they have a > > directory where they and the user can store bundles depending on their > > type (normal bundles and PARs). I assume that they parse the metadata > > and use it to resolve the needed bundles. > > At first I was happy that they are going to use OBR, fact that will > > gong to give a boost to OBR but unfortunately they are not. But maybe > > yo can convince them to have a plug-able design and be able to switch > > or combine with the simple mode they have. My guess that they go for > > this approach as is quite simple for the end user to just put a bundle > > in a directory and do not edit any xml/metadata. > > > > Alin > > > > On Thu, May 1, 2008 at 7:31 PM, Richard S. Hall > wrote: > > > > > > > For those who haven't seen this related announcement to the Spring > > > Application Platform, they also announced a bundle repository: > > > > > > http://www.springsource.com/repository/app/faq > > > > > > Not sure what this means for us with respect to Felix Commons, but it > is > > > something that we should probably investigate in some way. > > > > > > -> richard > > > > > > > > > > > >