Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 52345 invoked by uid 500); 29 Nov 2001 16:40:36 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 52330 invoked from network); 29 Nov 2001 16:40:35 -0000 Message-ID: <47FD4196C273D411950300508BCF19780170A5AD@S0001EXC0006> From: Tom Jordahl To: "'axis-dev@xml.apache.org'" Cc: "'soap-dev@xml.apache.org'" Subject: FW: PROPOSAL: New name for combined SOAP implementation project Date: Thu, 29 Nov 2001 11:40:22 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Just wondering - what's wrong with just keeping "Axis"? Its already > a pretty generic name. +1 I like the name Axis, and it seems like we have already gone through a name picking process at the time the Axis project was created. I am unclear on what exactly will happen. Will we merge the Apache SOAP code in to the Axis source? Will we merge Axis in to the SOAP code? Will we start a new tree, and use WASP as the starting point? What exactly do we expect to change about Axis development if we do this? -- Tom Jordahl Macromedia -----Original Message----- From: Doug Davis [mailto:dug@us.ibm.com] Sent: Wednesday, November 28, 2001 9:33 PM To: soap-dev@xml.apache.org Cc: Axis Development List Subject: Re: PROPOSAL: New name for combined SOAP implementation project Just wondering - what's wrong with just keeping "Axis"? Its already a pretty generic name. -Dug "Sanjiva Weerawarana" on 11/28/2001 08:09:58 PM Please respond to soap-dev@xml.apache.org To: "Apache SOAP" , "Axis Development List" cc: Subject: PROPOSAL: New name for combined SOAP implementation project In recent weeks there was a discussion on general@xml.apache.org about combining the SOAP implementation efforts in Apache into one project. Longer term, other Web services efforts may also be added to this same combined project. The main motivation for combining these efforts is to make the community stronger by combining the now separated communities. We have 3 separate SOAP implementations at hand (listed in historical order): - Apache SOAP - Apache Axis - WASP - a contribution from Systinet that's yet to be committed The proposal is to combine the three to form one SOAP implementation project at Apache. Apache SOAP is now the historical implementation and Axis is intended to be a replacement for it. WASP should be used in evolving Axis to basically take the best of both and make the next major rewrite of Apache's SOAP implementation. So, in order to get moving on this we have to agree on a name for the combined SOAP implementation project. What I suggest is that we come up with a few suggestions and then have a vote. To start the process I propose the name "ceylon" .. it comes from a random chat that Dims and I had during some of the preparation for this note! Let's spend a few days coming up with candidate names and then narrow down a list and call a vote. Bye, Sanjiva.