Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (nike.apache.org: domain of rickmcg@gmail.com designates
 74.125.92.26 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:user-agent:mime-version:to:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=mgsxx/nVH9kUlMvVhxPl2XDK+jVyej5QCDaTl7ZkLkIExLM3z6Q4cmSOjge1CDFtKi
         ttESsotnp4U62Xm8TK86FG2LB3AO7AciQycz2P6YncGBzZ+Sb8secXWgpkl/N96RoC2V
         gCIkmkYSwQDEyo+e3UskVFEQBX/kNTO1edL7I=
Message-ID: <49BFA685.90301@gmail.com>
Date: Tue, 17 Mar 2009 09:32:53 -0400
From: Rick McGuire <rickmcg@gmail.com>
Reply-To: rickmcg@gmail.com
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: [OSGi] Support for RFC 124?
References: <19e0530f0903170558s2048dd2cy1ca802639fb7c9b5@mail.gmail.com>
 <b23ecedc0903170619s2d912c76y8958cfdaebee7328@mail.gmail.com>
In-Reply-To: <b23ecedc0903170619s2d912c76y8958cfdaebee7328@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

It has been reworked much more that just the schema changes in the 
standardization process.  A lot of the service dynamics have changed, 
there have been some fairly signification changes to type conversions 
and property injection, a brand-new metadata API, new namespace handler 
support, etc. Springsource hasn't even implemented some of the new 
features yet, so this was far from a rubber-stamp effort.

Rick

Guillaume Nodet wrote:
> RFC 124 is simply a ruberstamp around what Spring-DM provides.  The 
> only real difference afaik are a few changes in the schema (mostly the 
> namespace and replacing "bean" by "component".
> This does not remove the usefulness of it btw...
>
> 2009/3/17 Davanum Srinivas <davanum@gmail.com <mailto:davanum@gmail.com>>
>
>     Folks,
>
>     Any interest in support for RFC 124, "A Component Model for OSGi"?
>     http://www.osgi.org/download/osgi-4.2-early-draft.pdf
>
>     This is in addition to typical J2EE artifacts that we already support.
>
>     thanks,
>     dims
>
>     --
>     Davanum Srinivas :: http://davanum.wordpress.com
>
>
>
>
> -- 
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
>