Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 4217 invoked from network); 29 Jan 2007 07:15:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Jan 2007 07:15:37 -0000 Received: (qmail 53701 invoked by uid 500); 29 Jan 2007 07:15:41 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 53644 invoked by uid 500); 29 Jan 2007 07:15:41 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 53633 invoked by uid 99); 29 Jan 2007 07:15:41 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Jan 2007 23:15:41 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of chamikaramj@gmail.com designates 66.249.92.175 as permitted sender) Received: from [66.249.92.175] (HELO ug-out-1314.google.com) (66.249.92.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Jan 2007 23:15:33 -0800 Received: by ug-out-1314.google.com with SMTP id j40so1083289ugd for ; Sun, 28 Jan 2007 23:15:11 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=mviTDenQkGL02HFIMIr651RRYVT99+rRz4QJkPs2R+zEGWNLOhWaJSJYx2oDwh8Pdetsk4YjYIKxhNHbGadZXA0cKwmS2zY6w47gHjCfgNPkyFuad7H+phVw9XghzXT3mght6PvkuAEHmenc24H6s60x1sUoCJjCfoIf3qvE4DQ= Received: by 10.82.163.13 with SMTP id l13mr3155955bue.1170054911478; Sun, 28 Jan 2007 23:15:11 -0800 (PST) Received: by 10.82.114.11 with HTTP; Sun, 28 Jan 2007 23:15:11 -0800 (PST) Message-ID: <9d4ec10b0701282315m5b578675ke61ae76a6a529df0@mail.gmail.com> Date: Mon, 29 Jan 2007 12:45:11 +0530 From: "Chamikara Jayalath" To: axis-dev@ws.apache.org Subject: Re: [Axis2] Issues with the current code base In-Reply-To: <45BD9023.4050008@opensource.lk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_80156_4404745.1170054911207" References: <45BD9023.4050008@opensource.lk> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_80156_4404745.1170054911207 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 1/29/07, Deepal Jayasinghe wrote: > > Hi all; > > I just went though the current code base and realized that > MessageContext code has been changed a lot . I found few issues with the > code base and hope we need to fix them. So I thought of sending this > mail for everyone's consideration. > > Well someone please explain to me whose going to need MessageContext > serialization , > Chamikara : Do you want that for Sandesha ? Currently no. But Matt had mentioned that he is working on something that uses this. Matt ? Ruchith : Do you want that for Security ? > > If none of you want this , who else need this ? > I am asking this question b'coz introduction of MC serialization we have > the following for each req. > - When ever Axis2 received a message it calls > activateMessageContext(msgContext); > - And what that does is , it calls mc.activate(engineContext); method > > Unfortunately that method is TOO long and was very difficult to > understand :). Ann can you simplify the method (that will be very helpful) > . > > In the meantime code convention in MC has changed a lot and need to have > very consistent code convention, please do not differ form that. > > Among the all , the most worst thing I saw in the code is following kind > of things, I strongly believe we should not have this kind of code in > the code base, If you found such kind of code please point out them then > and there. > > - String tmpClassNameStr = "null"; (is this the way we initialize to > NULL ) > - String tmpHasList = "no list" > - Unnecessary casting > - A number of unused variables > - Variable declarations here and there (as an example private static > final String - selfManagedDataDelimiter = "*";) > > In addition to that someone has added code to change OutInAxisOperation > name in the client side temporally, can I know why ? > > So please comment your ideas on this. > > Thanks > Deepal > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-dev-help@ws.apache.org > > ------=_Part_80156_4404745.1170054911207 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 1/29/07, Deepal Jayasinghe <deepal@opensource.lk> wrote:
Hi all;

I just went though the current code base and realized that
MessageContext code has been changed a lot . I found few issues with the
code base and hope we need to fix them. So I thought of sending this
mail for everyone's consideration.

Well someone please explain to me whose going to need MessageContext
serialization ,
Chamikara : Do you want that for Sandesha ?

Currently no. But Matt had mentioned that he is working on something that uses this.
Matt ?

Ruchith : Do you want that for Security ?

If none of you want this , who else need this ?
I am asking this question b'coz introduction of MC serialization we have
the following for each req.
- When ever Axis2 received a message it calls
activateMessageContext(msgContext);
- And what that does is , it calls mc.activate(engineContext); method

Unfortunately that method is TOO long and was very difficult to
understand :). Ann can you simplify the method (that will be very helpful) .

In the meantime code convention in MC has changed a lot and need to have
very consistent code convention, please do not differ form that.

Among the all , the most worst thing I saw in the code is following kind
of things, I strongly believe we should not have this kind of code in
the code base, If you found such kind of code please point out them then
and there.

- String tmpClassNameStr = "null";   (is this the way we initialize to
NULL )
- String tmpHasList      = "no list"
- Unnecessary casting
- A number of unused variables
- Variable declarations here and there  (as an example private static
final String  - selfManagedDataDelimiter = "*";)

In addition to that someone has added code to change OutInAxisOperation
name in the client side temporally, can I know why  ?

So please comment your ideas on this.

Thanks
Deepal



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


------=_Part_80156_4404745.1170054911207--