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

[Dan Diephouse]

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