cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Hogstrom <>
Subject Re: [COMMENT] Migrate Project Yoko from Incubator to Geronimo / CXF
Date Mon, 10 Dec 2007 18:44:53 GMT
Apache Geronimo has completed their voting process and voted to accept  
the Yoko project as outlined in the proposal.  When this vote is  
finalized I'll take the recommendation to the IPMC for their approval  
and we'll work out the logistics after that.


On Dec 6, 2007, at 10:22 AM, 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.
> -- 
> J. Daniel Kulp
> Principal Engineer
> P: 781-902-8727    C: 508-380-7194

View raw message