aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: [VOTE] Create new subproject Aries Remote Service Admin with initial code from CXF DOSGi
Date Tue, 08 Mar 2016 07:36:33 GMT
+1

Regards
JB

On 03/07/2016 05:06 PM, Christian Schneider wrote:
> In my previous mail I started a discussion about moving the CXF DOSGi
> code to Aries.
> As there was no negative feedback I am starting a vote to create a new
> subproject and move the non CXF specific code over to aries.
>
> I propose the name Aries Remote Service Admin (aries-rsa) as a name.
>
> The goal of the project is to implement the remote service admin spec in
> a very slim way with as few external dependencies as possible.
> A secondary goal is to provide an API for providers that allows to
> implement new transports and serializations in a very simple way.
>
> An initial code structure could look like this:
> /rsa
>      /parent
>      /core
>          /topology-manager
>          /provider-api
>          /rsa-core
>      /discovery
>          /local
>          /zookeeper
>      /provider
>          /rmi
>      /itests
>      /features
>      /examples
>
> The CXF specific provider will remain at CXF.
> I think we do not need to provide a full distribution like in CXF-DOSGi.
> A karaf feature should make sense though.
>
> To make it easy for current developers of CXF DOSGi to participate in
> the new development I propose that we keep the barrier low when voting
> for an aries committer if he is committer in CXF
> and already involved in CXF DOSGi.
>
> Please vote
>    [  ] +1 Create Aries Remote Service Admin subproject
>    [  ] -1 Do not
>
> Here is my
> +1
>
> Christian
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Mime
View raw message