Re: [Axis2] Convention violations/ inconsistencies

2006-10-04 Thread Rajith Attapattu
+1 to fix it, allthough this might break existing applications based on Axis2 might break.But it's better to correct a mistake than live with it. YMMVRegards,Rajith On 10/3/06, Afkham Azeez [EMAIL PROTECTED] wrote: Shall we go ahead and refactor these classes, or do we learn to live with this

Re: [Axis2] Convention violations/ inconsistencies

2006-10-04 Thread Sanjiva Weerawarana
+1 .. fixing this will make life easier for a large number of future users while causing an undue amount of pain to current users who came early and made Axis2 improve significantly. So .. how about a compromise; copy the code to the proper name and mark the old one deprecated. All the samples and

Re: [Axis2] Convention violations/ inconsistencies

2006-10-03 Thread Eran Chinthaka
You might wanna look at the names of these classes as well. RawXMLINOutMessageReceiver, RawXMLINOutAsyncMessageReceiver, RawXMLINOnlyMessageReceiver See how In and Out is written. But remember, lot of users must have used this name in their services.xml files :). -- Chinthaka Afkham Azeez

Re: [Axis2] Convention violations/ inconsistencies

2006-10-03 Thread Afkham Azeez
Shall we go ahead and refactor these classes, or do we learn to live with this mistake? :D If we are going to do it in the future, now's the best time (before 1.1)AzeezOn 10/3/06, Eran Chinthaka [EMAIL PROTECTED] wrote: You might wanna look at the names of these classes as

[Axis2] Convention violations/ inconsistencies

2006-10-02 Thread Afkham Azeez
Hi,There are a number of spelling mistakes/convention violations in some of the Axis2 API methods. e.g. public void disEngageModule(QName moduleName); Should be disengageModule(QName)In the axis2.xml the phase orders types named as follows:phaseOrder type=inflowphaseOrder type=outflowphaseOrder

Re: [Axis2] Convention violations/ inconsistencies

2006-10-02 Thread Bill Nagy
Please do. +1 -Bill On Mon, 2006-10-02 at 17:19 +0530, Afkham Azeez wrote: Hi, There are a number of spelling mistakes/convention violations in some of the Axis2 API methods. e.g. public void disEngageModule(QName moduleName); Should be disengageModule(QName) In the axis2.xml the

Re: [Axis2] Convention violations/ inconsistencies

2006-10-02 Thread Davanum Srinivas
+1 On 10/2/06, Bill Nagy [EMAIL PROTECTED] wrote: Please do. +1 -Bill On Mon, 2006-10-02 at 17:19 +0530, Afkham Azeez wrote: Hi, There are a number of spelling mistakes/convention violations in some of the Axis2 API methods. e.g. public void disEngageModule(QName moduleName); Should

Re: [Axis2] Convention violations/ inconsistencies

2006-10-02 Thread Thilina Gunarathne
+1.. Lets go ahead and do this before the release. Thilina On 10/3/06, Davanum Srinivas [EMAIL PROTECTED] wrote: +1 On 10/2/06, Bill Nagy [EMAIL PROTECTED] wrote: Please do. +1 -Bill On Mon, 2006-10-02 at 17:19 +0530, Afkham Azeez wrote: Hi, There are a number of spelling

Re: [Axis2] Convention violations/ inconsistencies

2006-10-02 Thread Eran Chinthaka
+1. At the same time please make sure you change all the places, especially look for places which has these names hard coded. I know the IDE you are using has very good support for this ;). -- Chinthaka Afkham Azeez wrote: Hi, There are a number of spelling mistakes/convention violations in