[PROPOSAL] Migrate Project Yoko from Incubator to Geronimo / CXF

[Matt Hogstrom]

The members of project yoko have been considering the future of Yoko  
as a project.  There have been several milestones delivered and the  
project is used by other ASF projects.   The project is not as active  
as other ASF projects and it makes sense to move the code from Yoko to  
other projects.  The Yoko team has the following proposal for your  
consideration.

Proposed Code Donation from Project Yoko to Apache CXF and Apache  
Geronimo

The Yoko community has been successful in delivering several  
milestones of the ORB implementation while in the Apache Incubator.  
These milestones are used by other Apache projects (namely Geronimo  
and Harmony) to support their releases.  The WebServices bindings are  
dependent on CXF.  The Yoko community has decided that the Yoko  
project does not have quite the momentum to carry itself as an  
independent project but has sufficient value for other projects for  
them to consider receiving the code and committers for that code-base  
as sub-projects.  Since the code under consideration is used by Apache  
Geronimo, Apache CXF and Apache Harmony the movement of the code  
should continue to allow for independent releases so the code can be  
easily shared with other dependent projects.

The proposed division is:

yoko-spec-corba - this is the org.omg interface classes.
rmi-spec - this is the javax.rmi spec implementation
core - This is the actual ORB implementation.
rmi-impl - This is the implementation of the RMIIIOP support.

These modules are also used by Harmony.

In addition to the code we propose that the following committers in  
Apache Yoko be accepted as committers in Apache Geronimo given their  
demonstration of delivering code, creating releases and functioning as  
a community.  Those noted with asterisks are already Geronimo  
committers.

Continued involvement with the core:

Rick McGuire *
David Jencks *
Alan Cabrera  *
Lars Kuhne
Alexey Petrenko
Darren Middleman

The remainder of the modules in Yoko are part of the webservices  
support and are independent of the underlying ORB implementation.

api -- interface classes used for the web services support.
bindings -- code to implement the CORBA-Web services bindings.
tools -- tools for generation WSDL and IDL for the bindings
maven-plugin -- some maven plugins that can use the tools for  
generating binding-related build artifacts.  None of the maven-plugin  
code is used by the ORB.

There is also a distribution directory with some sample applications.  
One set of samples demonstrates using the core ORB, the other set is  
for WebServices.  We recommend that the distribution directory should  
move to Apache CXF as the webservices examples use the orb samples to  
bind them as web services.  Since Apache Geronimo's only use of CORBA  
is for exporting EJBs, these samples are not particularly valuable for  
Geronimo.

The Yoko community did not have any committers that expressed an  
interest in continuing work on these bindings.  As such, only the code  
would be moving to apache CXF.

[dkulp]

I just want to go on record as saying I COMPLETELY support this and think
the CXF parts of this makes a lot of sense for the CXF project.   I've
always felt the binding parts of Yoko should have been done in CXF to
start off with.  

For those that aren't familliar with it, the yoko ws binding stuff
described in the proposal provides some tooling and a corba binding for
CXF.   It allows a CXF client (like a JAX-WS/JAXB client, but should
work with the other frontends) to talk to CORBA servers or for a CXF
server to be exposed as a CORBA server so other CORBA apps can talk to
it.


Anyway, Matt wants a vote to accept the proposal or not, but I'd like to
leave this open for discussion for a couple days first as I'd like to
hear others thoughts about it.

Dan


On Friday 30 November 2007, Matt Hogstrom wrote:

> The members of project yoko have been considering the future of Yoko
> as a project.  There have been several milestones delivered and the
> project is used by other ASF projects.   The project is not as active
> as other ASF projects and it makes sense to move the code from Yoko to
> other projects.  The Yoko team has the following proposal for your
> consideration.
>
> Proposed Code Donation from Project Yoko to Apache CXF and Apache
> Geronimo
>
> The Yoko community has been successful in delivering several
> milestones of the ORB implementation while in the Apache Incubator.
> These milestones are used by other Apache projects (namely Geronimo
> and Harmony) to support their releases.  The WebServices bindings are
> dependent on CXF.  The Yoko community has decided that the Yoko
> project does not have quite the momentum to carry itself as an
> independent project but has sufficient value for other projects for
> them to consider receiving the code and committers for that code-base
> as sub-projects.  Since the code under consideration is used by Apache
> Geronimo, Apache CXF and Apache Harmony the movement of the code
> should continue to allow for independent releases so the code can be
> easily shared with other dependent projects.
>
> The proposed division is:
>
> yoko-spec-corba - this is the org.omg interface classes.
> rmi-spec - this is the javax.rmi spec implementation
> core - This is the actual ORB implementation.
> rmi-impl - This is the implementation of the RMIIIOP support.
>
> These modules are also used by Harmony.
>
> In addition to the code we propose that the following committers in
> Apache Yoko be accepted as committers in Apache Geronimo given their
> demonstration of delivering code, creating releases and functioning as
> a community.  Those noted with asterisks are already Geronimo
> committers.
>
> Continued involvement with the core:
>
> Rick McGuire *
> David Jencks *
> Alan Cabrera  *
> Lars Kuhne
> Alexey Petrenko
> Darren Middleman
>
> The remainder of the modules in Yoko are part of the webservices
> support and are independent of the underlying ORB implementation.
>
> api -- interface classes used for the web services support.
> bindings -- code to implement the CORBA-Web services bindings.
> tools -- tools for generation WSDL and IDL for the bindings
> maven-plugin -- some maven plugins that can use the tools for
> generating binding-related build artifacts.  None of the maven-plugin
> code is used by the ORB.
>
> There is also a distribution directory with some sample applications.
> One set of samples demonstrates using the core ORB, the other set is
> for WebServices.  We recommend that the distribution directory should
> move to Apache CXF as the webservices examples use the orb samples to
> bind them as web services.  Since Apache Geronimo's only use of CORBA
> is for exporting EJBs, these samples are not particularly valuable for
> Geronimo.
>
> The Yoko community did not have any committers that expressed an
> interest in continuing work on these bindings.  As such, only the code
> would be moving to apache CXF.

--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
daniel.kulp@...
http://www.dankulp.com/blog

[Glen Mazza-2]

Just to make sure I understand this correctly, when you mean "corba
binding", you mean another transport, just like HTTP or JMS, correct?

Thanks,
Glen

Am Freitag, den 30.11.2007, 16:27 -0500 schrieb Daniel Kulp:

> I just want to go on record as saying I COMPLETELY support this and think
> the CXF parts of this makes a lot of sense for the CXF project.   I've
> always felt the binding parts of Yoko should have been done in CXF to
> start off with.  
>
> For those that aren't familliar with it, the yoko ws binding stuff
> described in the proposal provides some tooling and a corba binding for
> CXF.   It allows a CXF client (like a JAX-WS/JAXB client, but should
> work with the other frontends) to talk to CORBA servers or for a CXF
> server to be exposed as a CORBA server so other CORBA apps can talk to
> it.
>
>
> Anyway, Matt wants a vote to accept the proposal or not, but I'd like to
> leave this open for discussion for a couple days first as I'd like to
> hear others thoughts about it.
>
> Dan

[dkulp]

Well, by CORBA, I really mean IIOP, but that's a detail.

Basically, it's a combination binding (like soap) + transport (http)
where the JAXB (for example) objects get mashalled down to corba
streamables (instead of soap) and send on the wire via the IIOP stuff.  

The tooling is basically tools to do things like:
idl -> wsdl
wsdl -> idl
wsdl -> "wsdl with corba binding defined"
etc...

Dan



On Friday 30 November 2007, Glen Mazza wrote:

> Just to make sure I understand this correctly, when you mean "corba
> binding", you mean another transport, just like HTTP or JMS, correct?
>
> Thanks,
> Glen
>
> Am Freitag, den 30.11.2007, 16:27 -0500 schrieb Daniel Kulp:
> > I just want to go on record as saying I COMPLETELY support this and
> > think the CXF parts of this makes a lot of sense for the CXF
> > project.   I've always felt the binding parts of Yoko should have
> > been done in CXF to start off with.
> >
> > For those that aren't familliar with it, the yoko ws binding stuff
> > described in the proposal provides some tooling and a corba binding
> > for CXF.   It allows a CXF client (like a JAX-WS/JAXB client, but
> > should work with the other frontends) to talk to CORBA servers or
> > for a CXF server to be exposed as a CORBA server so other CORBA apps
> > can talk to it.
> >
> >
> > Anyway, Matt wants a vote to accept the proposal or not, but I'd
> > like to leave this open for discussion for a couple days first as
> > I'd like to hear others thoughts about it.
> >
> > Dan

--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
daniel.kulp@...
http://www.dankulp.com/blog

[Dan Diephouse-2]

I definitely support this move as well and agree with Dan K. that they make more sense in CXF than in the project anyway.

Cheers,
- Dan

Daniel Kulp wrote:

I just want to go on record as saying I COMPLETELY support this and think 
the CXF parts of this makes a lot of sense for the CXF project.   I've 
always felt the binding parts of Yoko should have been done in CXF to 
start off with.   

For those that aren't familliar with it, the yoko ws binding stuff 
described in the proposal provides some tooling and a corba binding for 
CXF.   It allows a CXF client (like a JAX-WS/JAXB client, but should 
work with the other frontends) to talk to CORBA servers or for a CXF 
server to be exposed as a CORBA server so other CORBA apps can talk to 
it.


Anyway, Matt wants a vote to accept the proposal or not, but I'd like to 
leave this open for discussion for a couple days first as I'd like to 
hear others thoughts about it.

Dan


On Friday 30 November 2007, Matt Hogstrom wrote:
  

The members of project yoko have been considering the future of Yoko
as a project.  There have been several milestones delivered and the
project is used by other ASF projects.   The project is not as active
as other ASF projects and it makes sense to move the code from Yoko to
other projects.  The Yoko team has the following proposal for your
consideration.

Proposed Code Donation from Project Yoko to Apache CXF and Apache
Geronimo

The Yoko community has been successful in delivering several
milestones of the ORB implementation while in the Apache Incubator.
These milestones are used by other Apache projects (namely Geronimo
and Harmony) to support their releases.  The WebServices bindings are
dependent on CXF.  The Yoko community has decided that the Yoko
project does not have quite the momentum to carry itself as an
independent project but has sufficient value for other projects for
them to consider receiving the code and committers for that code-base
as sub-projects.  Since the code under consideration is used by Apache
Geronimo, Apache CXF and Apache Harmony the movement of the code
should continue to allow for independent releases so the code can be
easily shared with other dependent projects.

The proposed division is:

yoko-spec-corba - this is the org.omg interface classes.
rmi-spec - this is the javax.rmi spec implementation
core - This is the actual ORB implementation.
rmi-impl - This is the implementation of the RMIIIOP support.

These modules are also used by Harmony.

In addition to the code we propose that the following committers in
Apache Yoko be accepted as committers in Apache Geronimo given their
demonstration of delivering code, creating releases and functioning as
a community.  Those noted with asterisks are already Geronimo
committers.

Continued involvement with the core:

Rick McGuire *
David Jencks *
Alan Cabrera  *
Lars Kuhne
Alexey Petrenko
Darren Middleman

The remainder of the modules in Yoko are part of the webservices
support and are independent of the underlying ORB implementation.

api -- interface classes used for the web services support.
bindings -- code to implement the CORBA-Web services bindings.
tools -- tools for generation WSDL and IDL for the bindings
maven-plugin -- some maven plugins that can use the tools for
generating binding-related build artifacts.  None of the maven-plugin
code is used by the ORB.

There is also a distribution directory with some sample applications.
One set of samples demonstrates using the core ORB, the other set is
for WebServices.  We recommend that the distribution directory should
move to Apache CXF as the webservices examples use the orb samples to
bind them as web services.  Since Apache Geronimo's only use of CORBA
is for exporting EJBs, these samples are not particularly valuable for
Geronimo.

The Yoko community did not have any committers that expressed an
interest in continuing work on these bindings.  As such, only the code
would be moving to apache CXF.
    

[James Mao]

But we should also do the interop test as well if we migrate it from
YOKO, right?
With Orbix?

James

> Well, by CORBA, I really mean IIOP, but that's a detail.
>
> Basically, it's a combination binding (like soap) + transport (http)
> where the JAXB (for example) objects get mashalled down to corba
> streamables (instead of soap) and send on the wire via the IIOP stuff.  
>
> The tooling is basically tools to do things like:
> idl -> wsdl
> wsdl -> idl
> wsdl -> "wsdl with corba binding defined"
> etc...
>
> Dan
>
>
>
> On Friday 30 November 2007, Glen Mazza wrote:
>  
>> Just to make sure I understand this correctly, when you mean "corba
>> binding", you mean another transport, just like HTTP or JMS, correct?
>>
>> Thanks,
>> Glen
>>
>> Am Freitag, den 30.11.2007, 16:27 -0500 schrieb Daniel Kulp:
>>    
>>> I just want to go on record as saying I COMPLETELY support this and
>>> think the CXF parts of this makes a lot of sense for the CXF
>>> project.   I've always felt the binding parts of Yoko should have
>>> been done in CXF to start off with.
>>>
>>> For those that aren't familliar with it, the yoko ws binding stuff
>>> described in the proposal provides some tooling and a corba binding
>>> for CXF.   It allows a CXF client (like a JAX-WS/JAXB client, but
>>> should work with the other frontends) to talk to CORBA servers or
>>> for a CXF server to be exposed as a CORBA server so other CORBA apps
>>> can talk to it.
>>>
>>>
>>> Anyway, Matt wants a vote to accept the proposal or not, but I'd
>>> like to leave this open for discussion for a couple days first as
>>> I'd like to hear others thoughts about it.
>>>
>>> Dan
>>>      
>
>
>
>  

[Alan D. Cabrera-2]

Thanks Matt.

It seems that no one objects.  Is the next step to have the recipient  
PMCs vote on receiving the code and developers?


Regards,
Alan

On Nov 30, 2007, at 9:54 AM, Matt Hogstrom wrote:

> The members of project yoko have been considering the future of Yoko  
> as a project.  There have been several milestones delivered and the  
> project is used by other ASF projects.   The project is not as  
> active as other ASF projects and it makes sense to move the code  
> from Yoko to other projects.  The Yoko team has the following  
> proposal for your consideration.
>
> Proposed Code Donation from Project Yoko to Apache CXF and Apache  
> Geronimo
>
> The Yoko community has been successful in delivering several  
> milestones of the ORB implementation while in the Apache Incubator.  
> These milestones are used by other Apache projects (namely Geronimo  
> and Harmony) to support their releases.  The WebServices bindings  
> are dependent on CXF.  The Yoko community has decided that the Yoko  
> project does not have quite the momentum to carry itself as an  
> independent project but has sufficient value for other projects for  
> them to consider receiving the code and committers for that code-
> base as sub-projects.  Since the code under consideration is used by  
> Apache Geronimo, Apache CXF and Apache Harmony the movement of the  
> code should continue to allow for independent releases so the code  
> can be easily shared with other dependent projects.
>
> The proposed division is:
>
> yoko-spec-corba - this is the org.omg interface classes.
> rmi-spec - this is the javax.rmi spec implementation
> core - This is the actual ORB implementation.
> rmi-impl - This is the implementation of the RMIIIOP support.
>
> These modules are also used by Harmony.
>
> In addition to the code we propose that the following committers in  
> Apache Yoko be accepted as committers in Apache Geronimo given their  
> demonstration of delivering code, creating releases and functioning  
> as a community.  Those noted with asterisks are already Geronimo  
> committers.
>
> Continued involvement with the core:
>
> Rick McGuire *
> David Jencks *
> Alan Cabrera  *
> Lars Kuhne
> Alexey Petrenko
> Darren Middleman
>
> The remainder of the modules in Yoko are part of the webservices  
> support and are independent of the underlying ORB implementation.
>
> api -- interface classes used for the web services support.
> bindings -- code to implement the CORBA-Web services bindings.
> tools -- tools for generation WSDL and IDL for the bindings
> maven-plugin -- some maven plugins that can use the tools for  
> generating binding-related build artifacts.  None of the maven-
> plugin code is used by the ORB.
>
> There is also a distribution directory with some sample  
> applications.  One set of samples demonstrates using the core ORB,  
> the other set is for WebServices.  We recommend that the  
> distribution directory should move to Apache CXF as the webservices  
> examples use the orb samples to bind them as web services.  Since  
> Apache Geronimo's only use of CORBA is for exporting EJBs, these  
> samples are not particularly valuable for Geronimo.
>
> The Yoko community did not have any committers that expressed an  
> interest in continuing work on these bindings.  As such, only the  
> code would be moving to apache CXF.
>

[Alan D. Cabrera-2]

Opps.  Mail threading is borked.  There seems to be some discussion  
going on still.


Regards,
Alan

On Dec 3, 2007, at 11:20 PM, Alan D. Cabrera wrote:

> Thanks Matt.
>
> It seems that no one objects.  Is the next step to have the  
> recipient PMCs vote on receiving the code and developers?
>
>
> Regards,
> Alan
>
> On Nov 30, 2007, at 9:54 AM, Matt Hogstrom wrote:
>
>> The members of project yoko have been considering the future of  
>> Yoko as a project.  There have been several milestones delivered  
>> and the project is used by other ASF projects.   The project is not  
>> as active as other ASF projects and it makes sense to move the code  
>> from Yoko to other projects.  The Yoko team has the following  
>> proposal for your consideration.
>>
>> Proposed Code Donation from Project Yoko to Apache CXF and Apache  
>> Geronimo
>>
>> The Yoko community has been successful in delivering several  
>> milestones of the ORB implementation while in the Apache  
>> Incubator.  These milestones are used by other Apache projects  
>> (namely Geronimo and Harmony) to support their releases.  The  
>> WebServices bindings are dependent on CXF.  The Yoko community has  
>> decided that the Yoko project does not have quite the momentum to  
>> carry itself as an independent project but has sufficient value for  
>> other projects for them to consider receiving the code and  
>> committers for that code-base as sub-projects.  Since the code  
>> under consideration is used by Apache Geronimo, Apache CXF and  
>> Apache Harmony the movement of the code should continue to allow  
>> for independent releases so the code can be easily shared with  
>> other dependent projects.
>>
>> The proposed division is:
>>
>> yoko-spec-corba - this is the org.omg interface classes.
>> rmi-spec - this is the javax.rmi spec implementation
>> core - This is the actual ORB implementation.
>> rmi-impl - This is the implementation of the RMIIIOP support.
>>
>> These modules are also used by Harmony.
>>
>> In addition to the code we propose that the following committers in  
>> Apache Yoko be accepted as committers in Apache Geronimo given  
>> their demonstration of delivering code, creating releases and  
>> functioning as a community.  Those noted with asterisks are already  
>> Geronimo committers.
>>
>> Continued involvement with the core:
>>
>> Rick McGuire *
>> David Jencks *
>> Alan Cabrera  *
>> Lars Kuhne
>> Alexey Petrenko
>> Darren Middleman
>>
>> The remainder of the modules in Yoko are part of the webservices  
>> support and are independent of the underlying ORB implementation.
>>
>> api -- interface classes used for the web services support.
>> bindings -- code to implement the CORBA-Web services bindings.
>> tools -- tools for generation WSDL and IDL for the bindings
>> maven-plugin -- some maven plugins that can use the tools for  
>> generating binding-related build artifacts.  None of the maven-
>> plugin code is used by the ORB.
>>
>> There is also a distribution directory with some sample  
>> applications.  One set of samples demonstrates using the core ORB,  
>> the other set is for WebServices.  We recommend that the  
>> distribution directory should move to Apache CXF as the webservices  
>> examples use the orb samples to bind them as web services.  Since  
>> Apache Geronimo's only use of CORBA is for exporting EJBs, these  
>> samples are not particularly valuable for Geronimo.
>>
>> The Yoko community did not have any committers that expressed an  
>> interest in continuing work on these bindings.  As such, only the  
>> code would be moving to apache CXF.
>>
>
>

[Ulhas Bhole]

I also would like to see it coming in CXF so I support it.

-- Ulhas Bhole

Dan Diephouse wrote:

> I definitely support this move as well and agree with Dan K. that they
> make more sense in CXF than in the project anyway.
>
> Cheers,
> - Dan
>
> Daniel Kulp wrote:
>> I just want to go on record as saying I COMPLETELY support this and think
>> the CXF parts of this makes a lot of sense for the CXF project.   I've
>> always felt the binding parts of Yoko should have been done in CXF to
>> start off with.  
>>
>> For those that aren't familliar with it, the yoko ws binding stuff
>> described in the proposal provides some tooling and a corba binding for
>> CXF.   It allows a CXF client (like a JAX-WS/JAXB client, but should
>> work with the other frontends) to talk to CORBA servers or for a CXF
>> server to be exposed as a CORBA server so other CORBA apps can talk to
>> it.
>>
>>
>> Anyway, Matt wants a vote to accept the proposal or not, but I'd like to
>> leave this open for discussion for a couple days first as I'd like to
>> hear others thoughts about it.
>>
>> Dan
>>
>>
>> On Friday 30 November 2007, Matt Hogstrom wrote:
>>  
>>> The members of project yoko have been considering the future of Yoko
>>> as a project.  There have been several milestones delivered and the
>>> project is used by other ASF projects.   The project is not as active
>>> as other ASF projects and it makes sense to move the code from Yoko to
>>> other projects.  The Yoko team has the following proposal for your
>>> consideration.
>>>
>>> Proposed Code Donation from Project Yoko to Apache CXF and Apache
>>> Geronimo
>>>
>>> The Yoko community has been successful in delivering several
>>> milestones of the ORB implementation while in the Apache Incubator.
>>> These milestones are used by other Apache projects (namely Geronimo
>>> and Harmony) to support their releases.  The WebServices bindings are
>>> dependent on CXF.  The Yoko community has decided that the Yoko
>>> project does not have quite the momentum to carry itself as an
>>> independent project but has sufficient value for other projects for
>>> them to consider receiving the code and committers for that code-base
>>> as sub-projects.  Since the code under consideration is used by Apache
>>> Geronimo, Apache CXF and Apache Harmony the movement of the code
>>> should continue to allow for independent releases so the code can be
>>> easily shared with other dependent projects.
>>>
>>> The proposed division is:
>>>
>>> yoko-spec-corba - this is the org.omg interface classes.
>>> rmi-spec - this is the javax.rmi spec implementation
>>> core - This is the actual ORB implementation.
>>> rmi-impl - This is the implementation of the RMIIIOP support.
>>>
>>> These modules are also used by Harmony.
>>>
>>> In addition to the code we propose that the following committers in
>>> Apache Yoko be accepted as committers in Apache Geronimo given their
>>> demonstration of delivering code, creating releases and functioning as
>>> a community.  Those noted with asterisks are already Geronimo
>>> committers.
>>>
>>> Continued involvement with the core:
>>>
>>> Rick McGuire *
>>> David Jencks *
>>> Alan Cabrera  *
>>> Lars Kuhne
>>> Alexey Petrenko
>>> Darren Middleman
>>>
>>> The remainder of the modules in Yoko are part of the webservices
>>> support and are independent of the underlying ORB implementation.
>>>
>>> api -- interface classes used for the web services support.
>>> bindings -- code to implement the CORBA-Web services bindings.
>>> tools -- tools for generation WSDL and IDL for the bindings
>>> maven-plugin -- some maven plugins that can use the tools for
>>> generating binding-related build artifacts.  None of the maven-plugin
>>> code is used by the ORB.
>>>
>>> There is also a distribution directory with some sample applications.
>>> One set of samples demonstrates using the core ORB, the other set is
>>> for WebServices.  We recommend that the distribution directory should
>>> move to Apache CXF as the webservices examples use the orb samples to
>>> bind them as web services.  Since Apache Geronimo's only use of CORBA
>>> is for exporting EJBs, these samples are not particularly valuable for
>>> Geronimo.
>>>
>>> The Yoko community did not have any committers that expressed an
>>> interest in continuing work on these bindings.  As such, only the code
>>> would be moving to apache CXF.
>>>    
>>
>>
>>
>>  
>
>
> --
> Dan Diephouse
> MuleSource
> http://mulesource.com | http://netzooid.com/blog

----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

[Ulhas Bhole]

Not necessarily, We can pickup the ORB component for test dependency on
other apache project where it will go from yoko.

-- Ulhas Bhole

James Mao wrote:

> But we should also do the interop test as well if we migrate it from
> YOKO, right?
> With Orbix?
>
> James
>
>> Well, by CORBA, I really mean IIOP, but that's a detail.
>>
>> Basically, it's a combination binding (like soap) + transport (http)
>> where the JAXB (for example) objects get mashalled down to corba
>> streamables (instead of soap) and send on the wire via the IIOP stuff.
>> The tooling is basically tools to do things like:
>> idl -> wsdl
>> wsdl -> idl
>> wsdl -> "wsdl with corba binding defined"
>> etc...
>>
>> Dan
>>
>>
>>
>> On Friday 30 November 2007, Glen Mazza wrote:
>>  
>>> Just to make sure I understand this correctly, when you mean "corba
>>> binding", you mean another transport, just like HTTP or JMS, correct?
>>>
>>> Thanks,
>>> Glen
>>>
>>> Am Freitag, den 30.11.2007, 16:27 -0500 schrieb Daniel Kulp:
>>>    
>>>> I just want to go on record as saying I COMPLETELY support this and
>>>> think the CXF parts of this makes a lot of sense for the CXF
>>>> project.   I've always felt the binding parts of Yoko should have
>>>> been done in CXF to start off with.
>>>>
>>>> For those that aren't familliar with it, the yoko ws binding stuff
>>>> described in the proposal provides some tooling and a corba binding
>>>> for CXF.   It allows a CXF client (like a JAX-WS/JAXB client, but
>>>> should work with the other frontends) to talk to CORBA servers or
>>>> for a CXF server to be exposed as a CORBA server so other CORBA apps
>>>> can talk to it.
>>>>
>>>>
>>>> Anyway, Matt wants a vote to accept the proposal or not, but I'd
>>>> like to leave this open for discussion for a couple days first as
>>>> I'd like to hear others thoughts about it.
>>>>
>>>> Dan
>>>>      
>>
>>
>>
>>  

----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

[dkulp]

This discussion has been open for a week now so I think we should go
ahead and call the vote.  

Basically, we are voting on the CXF parts of the proposal of accepting
the WS binding and tooling from the Yoko project.

Here is my +1



Dan


On Friday 30 November 2007, Matt Hogstrom wrote:

> The members of project yoko have been considering the future of Yoko
> as a project.  There have been several milestones delivered and the
> project is used by other ASF projects.   The project is not as active
> as other ASF projects and it makes sense to move the code from Yoko to
> other projects.  The Yoko team has the following proposal for your
> consideration.
>
> Proposed Code Donation from Project Yoko to Apache CXF and Apache
> Geronimo
>
> The Yoko community has been successful in delivering several
> milestones of the ORB implementation while in the Apache Incubator.
> These milestones are used by other Apache projects (namely Geronimo
> and Harmony) to support their releases.  The WebServices bindings are
> dependent on CXF.  The Yoko community has decided that the Yoko
> project does not have quite the momentum to carry itself as an
> independent project but has sufficient value for other projects for
> them to consider receiving the code and committers for that code-base
> as sub-projects.  Since the code under consideration is used by Apache
> Geronimo, Apache CXF and Apache Harmony the movement of the code
> should continue to allow for independent releases so the code can be
> easily shared with other dependent projects.
>
> The proposed division is:
>
> yoko-spec-corba - this is the org.omg interface classes.
> rmi-spec - this is the javax.rmi spec implementation
> core - This is the actual ORB implementation.
> rmi-impl - This is the implementation of the RMIIIOP support.
>
> These modules are also used by Harmony.
>
> In addition to the code we propose that the following committers in
> Apache Yoko be accepted as committers in Apache Geronimo given their
> demonstration of delivering code, creating releases and functioning as
> a community.  Those noted with asterisks are already Geronimo
> committers.
>
> Continued involvement with the core:
>
> Rick McGuire *
> David Jencks *
> Alan Cabrera  *
> Lars Kuhne
> Alexey Petrenko
> Darren Middleman
>
> The remainder of the modules in Yoko are part of the webservices
> support and are independent of the underlying ORB implementation.
>
> api -- interface classes used for the web services support.
> bindings -- code to implement the CORBA-Web services bindings.
> tools -- tools for generation WSDL and IDL for the bindings
> maven-plugin -- some maven plugins that can use the tools for
> generating binding-related build artifacts.  None of the maven-plugin
> code is used by the ORB.
>
> There is also a distribution directory with some sample applications.
> One set of samples demonstrates using the core ORB, the other set is
> for WebServices.  We recommend that the distribution directory should
> move to Apache CXF as the webservices examples use the orb samples to
> bind them as web services.  Since Apache Geronimo's only use of CORBA
> is for exporting EJBs, these samples are not particularly valuable for
> Geronimo.
>
> The Yoko community did not have any committers that expressed an
> interest in continuing work on these bindings.  As such, only the code
> would be moving to apache CXF.

--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
daniel.kulp@...
http://www.dankulp.com/blog

[bmargulies]

+1

-----Original Message-----
From: Daniel Kulp [mailto:dkulp@...]
Sent: Thu 12/6/2007 10:22 AM
To: cxf-dev@...
Cc: Matt Hogstrom
Subject: [VOTE][PROPOSAL] Migrate Project Yoko from Incubator to Geronimo / CXF
 

This discussion has been open for a week now so I think we should go
ahead and call the vote.  

Basically, we are voting on the CXF parts of the proposal of accepting
the WS binding and tooling from the Yoko project.

Here is my +1



Dan


On Friday 30 November 2007, Matt Hogstrom wrote:

> The members of project yoko have been considering the future of Yoko
> as a project.  There have been several milestones delivered and the
> project is used by other ASF projects.   The project is not as active
> as other ASF projects and it makes sense to move the code from Yoko to
> other projects.  The Yoko team has the following proposal for your
> consideration.
>
> Proposed Code Donation from Project Yoko to Apache CXF and Apache
> Geronimo
>
> The Yoko community has been successful in delivering several
> milestones of the ORB implementation while in the Apache Incubator.
> These milestones are used by other Apache projects (namely Geronimo
> and Harmony) to support their releases.  The WebServices bindings are
> dependent on CXF.  The Yoko community has decided that the Yoko
> project does not have quite the momentum to carry itself as an
> independent project but has sufficient value for other projects for
> them to consider receiving the code and committers for that code-base
> as sub-projects.  Since the code under consideration is used by Apache
> Geronimo, Apache CXF and Apache Harmony the movement of the code
> should continue to allow for independent releases so the code can be
> easily shared with other dependent projects.
>
> The proposed division is:
>
> yoko-spec-corba - this is the org.omg interface classes.
> rmi-spec - this is the javax.rmi spec implementation
> core - This is the actual ORB implementation.
> rmi-impl - This is the implementation of the RMIIIOP support.
>
> These modules are also used by Harmony.
>
> In addition to the code we propose that the following committers in
> Apache Yoko be accepted as committers in Apache Geronimo given their
> demonstration of delivering code, creating releases and functioning as
> a community.  Those noted with asterisks are already Geronimo
> committers.
>
> Continued involvement with the core:
>
> Rick McGuire *
> David Jencks *
> Alan Cabrera  *
> Lars Kuhne
> Alexey Petrenko
> Darren Middleman
>
> The remainder of the modules in Yoko are part of the webservices
> support and are independent of the underlying ORB implementation.
>
> api -- interface classes used for the web services support.
> bindings -- code to implement the CORBA-Web services bindings.
> tools -- tools for generation WSDL and IDL for the bindings
> maven-plugin -- some maven plugins that can use the tools for
> generating binding-related build artifacts.  None of the maven-plugin
> code is used by the ORB.
>
> There is also a distribution directory with some sample applications.
> One set of samples demonstrates using the core ORB, the other set is
> for WebServices.  We recommend that the distribution directory should
> move to Apache CXF as the webservices examples use the orb samples to
> bind them as web services.  Since Apache Geronimo's only use of CORBA
> is for exporting EJBs, these samples are not particularly valuable for
> Geronimo.
>
> The Yoko community did not have any committers that expressed an
> interest in continuing work on these bindings.  As such, only the code
> would be moving to apache CXF.

--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
daniel.kulp@...
http://www.dankulp.com/blog

+

[jgenender]

+1

Daniel Kulp wrote:

> This discussion has been open for a week now so I think we should go
> ahead and call the vote.  
>
> Basically, we are voting on the CXF parts of the proposal of accepting
> the WS binding and tooling from the Yoko project.
>
> Here is my +1
>
>
>
> Dan
>
>
> On Friday 30 November 2007, Matt Hogstrom wrote:
>> The members of project yoko have been considering the future of Yoko
>> as a project.  There have been several milestones delivered and the
>> project is used by other ASF projects.   The project is not as active
>> as other ASF projects and it makes sense to move the code from Yoko to
>> other projects.  The Yoko team has the following proposal for your
>> consideration.
>>
>> Proposed Code Donation from Project Yoko to Apache CXF and Apache
>> Geronimo
>>
>> The Yoko community has been successful in delivering several
>> milestones of the ORB implementation while in the Apache Incubator.
>> These milestones are used by other Apache projects (namely Geronimo
>> and Harmony) to support their releases.  The WebServices bindings are
>> dependent on CXF.  The Yoko community has decided that the Yoko
>> project does not have quite the momentum to carry itself as an
>> independent project but has sufficient value for other projects for
>> them to consider receiving the code and committers for that code-base
>> as sub-projects.  Since the code under consideration is used by Apache
>> Geronimo, Apache CXF and Apache Harmony the movement of the code
>> should continue to allow for independent releases so the code can be
>> easily shared with other dependent projects.
>>
>> The proposed division is:
>>
>> yoko-spec-corba - this is the org.omg interface classes.
>> rmi-spec - this is the javax.rmi spec implementation
>> core - This is the actual ORB implementation.
>> rmi-impl - This is the implementation of the RMIIIOP support.
>>
>> These modules are also used by Harmony.
>>
>> In addition to the code we propose that the following committers in
>> Apache Yoko be accepted as committers in Apache Geronimo given their
>> demonstration of delivering code, creating releases and functioning as
>> a community.  Those noted with asterisks are already Geronimo
>> committers.
>>
>> Continued involvement with the core:
>>
>> Rick McGuire *
>> David Jencks *
>> Alan Cabrera  *
>> Lars Kuhne
>> Alexey Petrenko
>> Darren Middleman
>>
>> The remainder of the modules in Yoko are part of the webservices
>> support and are independent of the underlying ORB implementation.
>>
>> api -- interface classes used for the web services support.
>> bindings -- code to implement the CORBA-Web services bindings.
>> tools -- tools for generation WSDL and IDL for the bindings
>> maven-plugin -- some maven plugins that can use the tools for
>> generating binding-related build artifacts.  None of the maven-plugin
>> code is used by the ORB.
>>
>> There is also a distribution directory with some sample applications.
>> One set of samples demonstrates using the core ORB, the other set is
>> for WebServices.  We recommend that the distribution directory should
>> move to Apache CXF as the webservices examples use the orb samples to
>> bind them as web services.  Since Apache Geronimo's only use of CORBA
>> is for exporting EJBs, these samples are not particularly valuable for
>> Geronimo.
>>
>> The Yoko community did not have any committers that expressed an
>> interest in continuing work on these bindings.  As such, only the code
>> would be moving to apache CXF.
>
>
>

[Paibir, Ajay]

 +1

Ajay

> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@...]
> Sent: 06 December 2007 15:22
> To: cxf-dev@...
> Cc: Matt Hogstrom
> Subject: [VOTE][PROPOSAL] Migrate Project Yoko from Incubator
> to Geronimo / CXF
>
>
> This discussion has been open for a week now so I think we
> should go ahead and call the vote.  
>
> Basically, we are voting on the CXF parts of the proposal of
> accepting the WS binding and tooling from the Yoko project.
>
> Here is my +1
>
>
>
> Dan
>
>
> On Friday 30 November 2007, Matt Hogstrom wrote:
> > The members of project yoko have been considering the
> future of Yoko
> > as a project.  There have been several milestones delivered and the
> > project is used by other ASF projects.   The project is not
> as active
> > as other ASF projects and it makes sense to move the code
> from Yoko to
> > other projects.  The Yoko team has the following proposal for your
> > consideration.
> >
> > Proposed Code Donation from Project Yoko to Apache CXF and Apache
> > Geronimo
> >
> > The Yoko community has been successful in delivering several
> > milestones of the ORB implementation while in the Apache Incubator.
> > These milestones are used by other Apache projects (namely Geronimo
> > and Harmony) to support their releases.  The WebServices
> bindings are
> > dependent on CXF.  The Yoko community has decided that the Yoko
> > project does not have quite the momentum to carry itself as an
> > independent project but has sufficient value for other projects for
> > them to consider receiving the code and committers for that
> code-base
> > as sub-projects.  Since the code under consideration is
> used by Apache
> > Geronimo, Apache CXF and Apache Harmony the movement of the code
> > should continue to allow for independent releases so the
> code can be
> > easily shared with other dependent projects.
> >
> > The proposed division is:
> >
> > yoko-spec-corba - this is the org.omg interface classes.
> > rmi-spec - this is the javax.rmi spec implementation core - This is
> > the actual ORB implementation.
> > rmi-impl - This is the implementation of the RMIIIOP support.
> >
> > These modules are also used by Harmony.
> >
> > In addition to the code we propose that the following committers in
> > Apache Yoko be accepted as committers in Apache Geronimo
> given their
> > demonstration of delivering code, creating releases and
> functioning as
> > a community.  Those noted with asterisks are already Geronimo
> > committers.
> >
> > Continued involvement with the core:
> >
> > Rick McGuire *
> > David Jencks *
> > Alan Cabrera  *
> > Lars Kuhne
> > Alexey Petrenko
> > Darren Middleman
> >
> > The remainder of the modules in Yoko are part of the webservices
> > support and are independent of the underlying ORB implementation.
> >
> > api -- interface classes used for the web services support.
> > bindings -- code to implement the CORBA-Web services bindings.
> > tools -- tools for generation WSDL and IDL for the bindings
> > maven-plugin -- some maven plugins that can use the tools for
> > generating binding-related build artifacts.  None of the
> maven-plugin
> > code is used by the ORB.
> >
> > There is also a distribution directory with some sample
> applications.
> > One set of samples demonstrates using the core ORB, the
> other set is
> > for WebServices.  We recommend that the distribution
> directory should
> > move to Apache CXF as the webservices examples use the orb
> samples to
> > bind them as web services.  Since Apache Geronimo's only
> use of CORBA
> > is for exporting EJBs, these samples are not particularly
> valuable for
> > Geronimo.
> >
> > The Yoko community did not have any committers that expressed an
> > interest in continuing work on these bindings.  As such,
> only the code
> > would be moving to apache CXF.
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727    C: 508-380-7194
> daniel.kulp@...
> http://www.dankulp.com/blog
>

----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

[Ulhas Bhole]

+1

-- Ulhas Bhole

Daniel Kulp wrote:

> This discussion has been open for a week now so I think we should go
> ahead and call the vote.  
>
> Basically, we are voting on the CXF parts of the proposal of accepting
> the WS binding and tooling from the Yoko project.
>
> Here is my +1
>
>
>
> Dan
>
>
> On Friday 30 November 2007, Matt Hogstrom wrote:
>  
>> The members of project yoko have been considering the future of Yoko
>> as a project.  There have been several milestones delivered and the
>> project is used by other ASF projects.   The project is not as active
>> as other ASF projects and it makes sense to move the code from Yoko to
>> other projects.  The Yoko team has the following proposal for your
>> consideration.
>>
>> Proposed Code Donation from Project Yoko to Apache CXF and Apache
>> Geronimo
>>
>> The Yoko community has been successful in delivering several
>> milestones of the ORB implementation while in the Apache Incubator.
>> These milestones are used by other Apache projects (namely Geronimo
>> and Harmony) to support their releases.  The WebServices bindings are
>> dependent on CXF.  The Yoko community has decided that the Yoko
>> project does not have quite the momentum to carry itself as an
>> independent project but has sufficient value for other projects for
>> them to consider receiving the code and committers for that code-base
>> as sub-projects.  Since the code under consideration is used by Apache
>> Geronimo, Apache CXF and Apache Harmony the movement of the code
>> should continue to allow for independent releases so the code can be
>> easily shared with other dependent projects.
>>
>> The proposed division is:
>>
>> yoko-spec-corba - this is the org.omg interface classes.
>> rmi-spec - this is the javax.rmi spec implementation
>> core - This is the actual ORB implementation.
>> rmi-impl - This is the implementation of the RMIIIOP support.
>>
>> These modules are also used by Harmony.
>>
>> In addition to the code we propose that the following committers in
>> Apache Yoko be accepted as committers in Apache Geronimo given their
>> demonstration of delivering code, creating releases and functioning as
>> a community.  Those noted with asterisks are already Geronimo
>> committers.
>>
>> Continued involvement with the core:
>>
>> Rick McGuire *
>> David Jencks *
>> Alan Cabrera  *
>> Lars Kuhne
>> Alexey Petrenko
>> Darren Middleman
>>
>> The remainder of the modules in Yoko are part of the webservices
>> support and are independent of the underlying ORB implementation.
>>
>> api -- interface classes used for the web services support.
>> bindings -- code to implement the CORBA-Web services bindings.
>> tools -- tools for generation WSDL and IDL for the bindings
>> maven-plugin -- some maven plugins that can use the tools for
>> generating binding-related build artifacts.  None of the maven-plugin
>> code is used by the ORB.
>>
>> There is also a distribution directory with some sample applications.
>> One set of samples demonstrates using the core ORB, the other set is
>> for WebServices.  We recommend that the distribution directory should
>> move to Apache CXF as the webservices examples use the orb samples to
>> bind them as web services.  Since Apache Geronimo's only use of CORBA
>> is for exporting EJBs, these samples are not particularly valuable for
>> Geronimo.
>>
>> The Yoko community did not have any committers that expressed an
>> interest in continuing work on these bindings.  As such, only the code
>> would be moving to apache CXF.
>>    
>
>
>
>  

----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

[James.Strachan]

+1

On 06/12/2007, Daniel Kulp <dkulp@...> wrote:

>
> This discussion has been open for a week now so I think we should go
> ahead and call the vote.
>
> Basically, we are voting on the CXF parts of the proposal of accepting
> the WS binding and tooling from the Yoko project.
>
> Here is my +1
>
>
>
> Dan
>
>
> On Friday 30 November 2007, Matt Hogstrom wrote:
> > The members of project yoko have been considering the future of Yoko
> > as a project.  There have been several milestones delivered and the
> > project is used by other ASF projects.   The project is not as active
> > as other ASF projects and it makes sense to move the code from Yoko to
> > other projects.  The Yoko team has the following proposal for your
> > consideration.
> >
> > Proposed Code Donation from Project Yoko to Apache CXF and Apache
> > Geronimo
> >
> > The Yoko community has been successful in delivering several
> > milestones of the ORB implementation while in the Apache Incubator.
> > These milestones are used by other Apache projects (namely Geronimo
> > and Harmony) to support their releases.  The WebServices bindings are
> > dependent on CXF.  The Yoko community has decided that the Yoko
> > project does not have quite the momentum to carry itself as an
> > independent project but has sufficient value for other projects for
> > them to consider receiving the code and committers for that code-base
> > as sub-projects.  Since the code under consideration is used by Apache
> > Geronimo, Apache CXF and Apache Harmony the movement of the code
> > should continue to allow for independent releases so the code can be
> > easily shared with other dependent projects.
> >
> > The proposed division is:
> >
> > yoko-spec-corba - this is the org.omg interface classes.
> > rmi-spec - this is the javax.rmi spec implementation
> > core - This is the actual ORB implementation.
> > rmi-impl - This is the implementation of the RMIIIOP support.
> >
> > These modules are also used by Harmony.
> >
> > In addition to the code we propose that the following committers in
> > Apache Yoko be accepted as committers in Apache Geronimo given their
> > demonstration of delivering code, creating releases and functioning as
> > a community.  Those noted with asterisks are already Geronimo
> > committers.
> >
> > Continued involvement with the core:
> >
> > Rick McGuire *
> > David Jencks *
> > Alan Cabrera  *
> > Lars Kuhne
> > Alexey Petrenko
> > Darren Middleman
> >
> > The remainder of the modules in Yoko are part of the webservices
> > support and are independent of the underlying ORB implementation.
> >
> > api -- interface classes used for the web services support.
> > bindings -- code to implement the CORBA-Web services bindings.
> > tools -- tools for generation WSDL and IDL for the bindings
> > maven-plugin -- some maven plugins that can use the tools for
> > generating binding-related build artifacts.  None of the maven-plugin
> > code is used by the ORB.
> >
> > There is also a distribution directory with some sample applications.
> > One set of samples demonstrates using the core ORB, the other set is
> > for WebServices.  We recommend that the distribution directory should
> > move to Apache CXF as the webservices examples use the orb samples to
> > bind them as web services.  Since Apache Geronimo's only use of CORBA
> > is for exporting EJBs, these samples are not particularly valuable for
> > Geronimo.
> >
> > The Yoko community did not have any committers that expressed an
> > interest in continuing work on these bindings.  As such, only the code
> > would be moving to apache CXF.
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727    C: 508-380-7194
> daniel.kulp@...
> http://www.dankulp.com/blog
>

--
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://open.iona.com

[peterjones]

+1

On Thu, Dec 06, 2007 at 10:22:26AM -0500, Daniel Kulp wrote:

>
> This discussion has been open for a week now so I think we should go
> ahead and call the vote.  
>
> Basically, we are voting on the CXF parts of the proposal of accepting
> the WS binding and tooling from the Yoko project.
>
> Here is my +1
>
>
>
> Dan
>
>
> On Friday 30 November 2007, Matt Hogstrom wrote:
> > The members of project yoko have been considering the future of Yoko
> > as a project.  There have been several milestones delivered and the
> > project is used by other ASF projects.   The project is not as active
> > as other ASF projects and it makes sense to move the code from Yoko to
> > other projects.  The Yoko team has the following proposal for your
> > consideration.
> >
> > Proposed Code Donation from Project Yoko to Apache CXF and Apache
> > Geronimo
> >
> > The Yoko community has been successful in delivering several
> > milestones of the ORB implementation while in the Apache Incubator.
> > These milestones are used by other Apache projects (namely Geronimo
> > and Harmony) to support their releases.  The WebServices bindings are
> > dependent on CXF.  The Yoko community has decided that the Yoko
> > project does not have quite the momentum to carry itself as an
> > independent project but has sufficient value for other projects for
> > them to consider receiving the code and committers for that code-base
> > as sub-projects.  Since the code under consideration is used by Apache
> > Geronimo, Apache CXF and Apache Harmony the movement of the code
> > should continue to allow for independent releases so the code can be
> > easily shared with other dependent projects.
> >
> > The proposed division is:
> >
> > yoko-spec-corba - this is the org.omg interface classes.
> > rmi-spec - this is the javax.rmi spec implementation
> > core - This is the actual ORB implementation.
> > rmi-impl - This is the implementation of the RMIIIOP support.
> >
> > These modules are also used by Harmony.
> >
> > In addition to the code we propose that the following committers in
> > Apache Yoko be accepted as committers in Apache Geronimo given their
> > demonstration of delivering code, creating releases and functioning as
> > a community.  Those noted with asterisks are already Geronimo
> > committers.
> >
> > Continued involvement with the core:
> >
> > Rick McGuire *
> > David Jencks *
> > Alan Cabrera  *
> > Lars Kuhne
> > Alexey Petrenko
> > Darren Middleman
> >
> > The remainder of the modules in Yoko are part of the webservices
> > support and are independent of the underlying ORB implementation.
> >
> > api -- interface classes used for the web services support.
> > bindings -- code to implement the CORBA-Web services bindings.
> > tools -- tools for generation WSDL and IDL for the bindings
> > maven-plugin -- some maven plugins that can use the tools for
> > generating binding-related build artifacts.  None of the maven-plugin
> > code is used by the ORB.
> >
> > There is also a distribution directory with some sample applications.
> > One set of samples demonstrates using the core ORB, the other set is
> > for WebServices.  We recommend that the distribution directory should
> > move to Apache CXF as the webservices examples use the orb samples to
> > bind them as web services.  Since Apache Geronimo's only use of CORBA
> > is for exporting EJBs, these samples are not particularly valuable for
> > Geronimo.
> >
> > The Yoko community did not have any committers that expressed an
> > interest in continuing work on these bindings.  As such, only the code
> > would be moving to apache CXF.

--
Peter Jones
IONA Technologies
E-Mail: mailto:peter.jones@...
Tel: [phone] x321 | Fax: [phone]
570 Newfoundland Drive, St. John's, NL, Canada A1A 5B1

[Glen Mazza-2]

Abstain.  I haven't researched the matter.

Am Donnerstag, den 06.12.2007, 10:22 -0500 schrieb Daniel Kulp:

> This discussion has been open for a week now so I think we should go
> ahead and call the vote.  
>
> Basically, we are voting on the CXF parts of the proposal of accepting
> the WS binding and tooling from the Yoko project.
>
> Here is my +1
>
>
>
> Dan
>
>
> On Friday 30 November 2007, Matt Hogstrom wrote:
> > The members of project yoko have been considering the future of Yoko
> > as a project.  There have been several milestones delivered and the
> > project is used by other ASF projects.   The project is not as active
> > as other ASF projects and it makes sense to move the code from Yoko to
> > other projects.  The Yoko team has the following proposal for your
> > consideration.
> >
> > Proposed Code Donation from Project Yoko to Apache CXF and Apache
> > Geronimo
> >
> > The Yoko community has been successful in delivering several
> > milestones of the ORB implementation while in the Apache Incubator.
> > These milestones are used by other Apache projects (namely Geronimo
> > and Harmony) to support their releases.  The WebServices bindings are
> > dependent on CXF.  The Yoko community has decided that the Yoko
> > project does not have quite the momentum to carry itself as an
> > independent project but has sufficient value for other projects for
> > them to consider receiving the code and committers for that code-base
> > as sub-projects.  Since the code under consideration is used by Apache
> > Geronimo, Apache CXF and Apache Harmony the movement of the code
> > should continue to allow for independent releases so the code can be
> > easily shared with other dependent projects.
> >
> > The proposed division is:
> >
> > yoko-spec-corba - this is the org.omg interface classes.
> > rmi-spec - this is the javax.rmi spec implementation
> > core - This is the actual ORB implementation.
> > rmi-impl - This is the implementation of the RMIIIOP support.
> >
> > These modules are also used by Harmony.
> >
> > In addition to the code we propose that the following committers in
> > Apache Yoko be accepted as committers in Apache Geronimo given their
> > demonstration of delivering code, creating releases and functioning as
> > a community.  Those noted with asterisks are already Geronimo
> > committers.
> >
> > Continued involvement with the core:
> >
> > Rick McGuire *
> > David Jencks *
> > Alan Cabrera  *
> > Lars Kuhne
> > Alexey Petrenko
> > Darren Middleman
> >
> > The remainder of the modules in Yoko are part of the webservices
> > support and are independent of the underlying ORB implementation.
> >
> > api -- interface classes used for the web services support.
> > bindings -- code to implement the CORBA-Web services bindings.
> > tools -- tools for generation WSDL and IDL for the bindings
> > maven-plugin -- some maven plugins that can use the tools for
> > generating binding-related build artifacts.  None of the maven-plugin
> > code is used by the ORB.
> >
> > There is also a distribution directory with some sample applications.
> > One set of samples demonstrates using the core ORB, the other set is
> > for WebServices.  We recommend that the distribution directory should
> > move to Apache CXF as the webservices examples use the orb samples to
> > bind them as web services.  Since Apache Geronimo's only use of CORBA
> > is for exporting EJBs, these samples are not particularly valuable for
> > Geronimo.
> >
> > The Yoko community did not have any committers that expressed an
> > interest in continuing work on these bindings.  As such, only the code
> > would be moving to apache CXF.
>
>
>

[Bozhong Lin]

+1

On Dec 6, 2007 11:22 PM, Daniel Kulp <dkulp@...> wrote:

>
> This discussion has been open for a week now so I think we should go
> ahead and call the vote.
>
> Basically, we are voting on the CXF parts of the proposal of accepting
> the WS binding and tooling from the Yoko project.
>
> Here is my +1
>
>
>
> Dan
>
>
> On Friday 30 November 2007, Matt Hogstrom wrote:
> > The members of project yoko have been considering the future of Yoko
> > as a project.  There have been several milestones delivered and the
> > project is used by other ASF projects.   The project is not as active
> > as other ASF projects and it makes sense to move the code from Yoko to
> > other projects.  The Yoko team has the following proposal for your
> > consideration.
> >
> > Proposed Code Donation from Project Yoko to Apache CXF and Apache
> > Geronimo
> >
> > The Yoko community has been successful in delivering several
> > milestones of the ORB implementation while in the Apache Incubator.
> > These milestones are used by other Apache projects (namely Geronimo
> > and Harmony) to support their releases.  The WebServices bindings are
> > dependent on CXF.  The Yoko community has decided that the Yoko
> > project does not have quite the momentum to carry itself as an
> > independent project but has sufficient value for other projects for
> > them to consider receiving the code and committers for that code-base
> > as sub-projects.  Since the code under consideration is used by Apache
> > Geronimo, Apache CXF and Apache Harmony the movement of the code
> > should continue to allow for independent releases so the code can be
> > easily shared with other dependent projects.
> >
> > The proposed division is:
> >
> > yoko-spec-corba - this is the org.omg interface classes.
> > rmi-spec - this is the javax.rmi spec implementation
> > core - This is the actual ORB implementation.
> > rmi-impl - This is the implementation of the RMIIIOP support.
> >
> > These modules are also used by Harmony.
> >
> > In addition to the code we propose that the following committers in
> > Apache Yoko be accepted as committers in Apache Geronimo given their
> > demonstration of delivering code, creating releases and functioning as
> > a community.  Those noted with asterisks are already Geronimo
> > committers.
> >
> > Continued involvement with the core:
> >
> > Rick McGuire *
> > David Jencks *
> > Alan Cabrera  *
> > Lars Kuhne
> > Alexey Petrenko
> > Darren Middleman
> >
> > The remainder of the modules in Yoko are part of the webservices
> > support and are independent of the underlying ORB implementation.
> >
> > api -- interface classes used for the web services support.
> > bindings -- code to implement the CORBA-Web services bindings.
> > tools -- tools for generation WSDL and IDL for the bindings
> > maven-plugin -- some maven plugins that can use the tools for
> > generating binding-related build artifacts.  None of the maven-plugin
> > code is used by the ORB.
> >
> > There is also a distribution directory with some sample applications.
> > One set of samples demonstrates using the core ORB, the other set is
> > for WebServices.  We recommend that the distribution directory should
> > move to Apache CXF as the webservices examples use the orb samples to
> > bind them as web services.  Since Apache Geronimo's only use of CORBA
> > is for exporting EJBs, these samples are not particularly valuable for
> > Geronimo.
> >
> > The Yoko community did not have any committers that expressed an
> > interest in continuing work on these bindings.  As such, only the code
> > would be moving to apache CXF.
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727    C: 508-380-7194
> daniel.kulp@...
> http://www.dankulp.com/blog
>

[Willem2]

My +1

Willem.

Daniel Kulp wrote:

> This discussion has been open for a week now so I think we should go
> ahead and call the vote.  
>
> Basically, we are voting on the CXF parts of the proposal of accepting
> the WS binding and tooling from the Yoko project.
>
> Here is my +1
>
>
>
> Dan
>
>
> On Friday 30 November 2007, Matt Hogstrom wrote:
>  
>> The members of project yoko have been considering the future of Yoko
>> as a project.  There have been several milestones delivered and the
>> project is used by other ASF projects.   The project is not as active
>> as other ASF projects and it makes sense to move the code from Yoko to
>> other projects.  The Yoko team has the following proposal for your
>> consideration.
>>
>> Proposed Code Donation from Project Yoko to Apache CXF and Apache
>> Geronimo
>>
>> The Yoko community has been successful in delivering several
>> milestones of the ORB implementation while in the Apache Incubator.
>> These milestones are used by other Apache projects (namely Geronimo
>> and Harmony) to support their releases.  The WebServices bindings are
>> dependent on CXF.  The Yoko community has decided that the Yoko
>> project does not have quite the momentum to carry itself as an
>> independent project but has sufficient value for other projects for
>> them to consider receiving the code and committers for that code-base
>> as sub-projects.  Since the code under consideration is used by Apache
>> Geronimo, Apache CXF and Apache Harmony the movement of the code
>> should continue to allow for independent releases so the code can be
>> easily shared with other dependent projects.
>>
>> The proposed division is:
>>
>> yoko-spec-corba - this is the org.omg interface classes.
>> rmi-spec - this is the javax.rmi spec implementation
>> core - This is the actual ORB implementation.
>> rmi-impl - This is the implementation of the RMIIIOP support.
>>
>> These modules are also used by Harmony.
>>
>> In addition to the code we propose that the following committers in
>> Apache Yoko be accepted as committers in Apache Geronimo given their
>> demonstration of delivering code, creating releases and functioning as
>> a community.  Those noted with asterisks are already Geronimo
>> committers.
>>
>> Continued involvement with the core:
>>
>> Rick McGuire *
>> David Jencks *
>> Alan Cabrera  *
>> Lars Kuhne
>> Alexey Petrenko
>> Darren Middleman
>>
>> The remainder of the modules in Yoko are part of the webservices
>> support and are independent of the underlying ORB implementation.
>>
>> api -- interface classes used for the web services support.
>> bindings -- code to implement the CORBA-Web services bindings.
>> tools -- tools for generation WSDL and IDL for the bindings
>> maven-plugin -- some maven plugins that can use the tools for
>> generating binding-related build artifacts.  None of the maven-plugin
>> code is used by the ORB.
>>
>> There is also a distribution directory with some sample applications.
>> One set of samples demonstrates using the core ORB, the other set is
>> for WebServices.  We recommend that the distribution directory should
>> move to Apache CXF as the webservices examples use the orb samples to
>> bind them as web services.  Since Apache Geronimo's only use of CORBA
>> is for exporting EJBs, these samples are not particularly valuable for
>> Geronimo.
>>
>> The Yoko community did not have any committers that expressed an
>> interest in continuing work on these bindings.  As such, only the code
>> would be moving to apache CXF.
>>    
>
>
>
>