Dims, It is a very good idea. WSDL2Java stuff is now included in axis, apllo, herms, muse, addressing. It is better if we can merge it to addressing, resource, notification, management,etc-enabled wsdl processor.
One thing, is there any 'ws-common-cvs' mailing list to get a commit log? Thanks ----- Original Message ----- From: "Davanum Srinivas" <[EMAIL PROTECTED]> To: <general@ws.apache.org> Sent: Saturday, June 04, 2005 5:04 AM Subject: Increasing cross project cooperation Hi all, Does anyone think that moving to a jakarta-commons/cocoon model where there is a single ACL for all of web services will help? We can still have separate release cycles for all projects., and each project can have a list of active participants. For example, i want the Axis/C++ folks (and the folks on Apollo/Hermes/Muse) to contribute to make WSDL2Java stuff better (to reduce duplication of code now in WSDL2Ws). Now with Axis2, if we can get everyone more involved (it's not too late yet!) now, it will ease the pains of "porting" existing code to Axis2...and so on. Basically, we will have 1 list on CVS/SVN with all web services committers and all of them will have rw privileges on all CVS/SVN modules. Existing committers who want to contribute to another sister WS project can sign up in the list of active folks for that project and help out with that project. Yes, we are all scared of folks changing stuff willy-nilly. But it just implies, we need to monitor changes more closely and work a bit more on mentoring others on our code. What do you all think? Thanks, dims -- Davanum Srinivas - http://webservices.apache.org/~dims/
