Return-Path: X-Original-To: apmail-axis-java-dev-archive@www.apache.org Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 72D8BF955 for ; Sat, 13 Apr 2013 13:40:40 +0000 (UTC) Received: (qmail 77301 invoked by uid 500); 13 Apr 2013 13:40:39 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 77185 invoked by uid 500); 13 Apr 2013 13:40:39 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 77175 invoked by uid 99); 13 Apr 2013 13:40:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Apr 2013 13:40:39 +0000 X-ASF-Spam-Status: No, hits=3.2 required=5.0 tests=DEAR_SOMETHING,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sagara.gunathunga@gmail.com designates 209.85.214.46 as permitted sender) Received: from [209.85.214.46] (HELO mail-bk0-f46.google.com) (209.85.214.46) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Apr 2013 13:40:34 +0000 Received: by mail-bk0-f46.google.com with SMTP id je9so1734998bkc.5 for ; Sat, 13 Apr 2013 06:40:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=y4yuxWh+PNQG7IMgQp596mE3X37G+n/HTSj3HgJNIvA=; b=mBvLV6SrYqwlue3f29i3hVaDI0j19hQI+xv63yuROS2IgwjDfOKZUHWOPW6lOHjVw/ ddMCij4zR2C1YQLj+s2iSS2HvSWE5z4FFN/gcCUKSDwN//htuTVE2zbUF1di7N5lVLnv fAS5mNyk5wUsUe6QNLa4qnzg2MJ/2jr9jsYz2u94Cr09gE/3qLsk/fUtcQf+7ypSIyuk w5QvB80zZpEw9WEwsC5Gk5qi+cM5m/kjy50jpriQ72gdy2qc2avWLaDH0oAUBVhnm0BM AQVY/4159T/3rIHSZ81bcr+E+YbbsgaPTW9gXZuw9EY/nckupKbLdXa55165Rmxit+1o MKwg== X-Received: by 10.205.119.19 with SMTP id fs19mr5624781bkc.105.1365860413548; Sat, 13 Apr 2013 06:40:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.40.141 with HTTP; Sat, 13 Apr 2013 06:39:52 -0700 (PDT) In-Reply-To: References: From: Sagara Gunathunga Date: Sat, 13 Apr 2013 19:09:52 +0530 Message-ID: Subject: Re: Improve Axis2 JAX-WS performance To: java-dev@axis.apache.org Content-Type: multipart/alternative; boundary=0015173fedfac368d804da3e28a6 X-Virus-Checked: Checked by ClamAV on apache.org --0015173fedfac368d804da3e28a6 Content-Type: text/plain; charset=ISO-8859-1 On Sat, Apr 13, 2013 at 5:54 PM, Danushka Seneviratne < danushkagsoc13@gmail.com> wrote: > Dear Sir/Madam, > > > While searching a GSoC project idea, I got to know about Axis2 project > having potential opportunity to work on its JAX-WS implementation. > According to the facts I gathered, I have created a JIRA issue here > https://issues.apache.org/jira/browse/AXIS2-5509. As foremost objective > I'm planning to find bottlenecks of Axis2 JAX-WS framework and suggest > possible solutions during the project period. I have some experience about > JAX-WS programming model but it is based on Metro framework on JBoss > server. During recent past I tried to develop few Axis2 based JAX-WS > services and managed to run set of basic samples. I'm much obliged if > someone can guide me to find out a direction. > Sometimes back I did a profiling to identify performance issues of JAX-WS implementation you can read what I found from here [1]. Based on my findings I started to write improved version of JAX-WS but couldn't manage to make much progress with my time restrictions, basically I wrote a custom MethodMarshaller[2] and plugged into the existing architecture. I'm not sure where I put those codes but I will try to find them so that you can take a look. If you really want to make this idea into GSoC project then it's required to understand issues on current architecture first but this depends on of how well you understand the architecture of existing implementation. My recommendation is spend some time initially and come up with detail proposal and detailed plan mentioning these are the identified issues and these are the possible ways of solution etc. Any way you have to be quick on preparation of this project. Hope this helps you to start your first step if you need further helps don't hesitate to contact this list. [1] - http://markmail.org/thread/7pww6veepr77kzuq [2] - http://axis.apache.org/axis2/java/core/api/org/apache/axis2/jaxws/marshaller/MethodMarshaller.html Thanks ! > > Thanks in advance > > > Danushka Seneviratne > > -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/ LinkedIn - http://www.linkedin.com/in/ssagara --0015173fedfac368d804da3e28a6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Sat, Apr 13, 2013 at 5:54 PM, Danushk= a Seneviratne <danushkagsoc13@gmail.com> wrote:

=

Dear Sir/Madam,


While searching a GSoC project idea, I got= to know about Axis2 project having potential opportunity to work on its JA= X-WS implementation. According to the facts I gathered, I have created a JI= RA issue here https://issues.apache.org/jira/browse/AXIS2-5509. As = foremost objective I'm planning to find bottlenecks of Axis2 JAX-WS fra= mework and suggest possible solutions during the project period. I have som= e experience about JAX-WS programming model but it is based on Metro framew= ork on JBoss server. During recent past I tried to develop few Axis2 based = JAX-WS services and managed to run set of basic samples. I'm much oblig= ed if someone can guide me to find out a direction.

=A0
Sometimes back I did a profiling to identify= performance issues of JAX-WS implementation you can read what I found from= here [1]. Based on my findings I started to write improved version of JAX-= WS but couldn't manage to make much progress with my time restrictions,= basically I wrote a custom MethodMarshaller[2] and plugged into the existi= ng architecture. I'm not sure where I put those codes but I will try to= find them so that you can take a look.

If you really want to make this idea into GSoC project then it's re= quired to understand issues on current architecture first but this depends = on of how well you understand the architecture of existing implementation. = My recommendation is spend some time initially and come up with detail prop= osal and detailed plan mentioning these are the identified issues and these= are the possible ways of solution etc. Any way you have to be quick on pre= paration of this project. Hope this helps you to start your first step if y= ou need further helps don't hesitate to contact this list.

[1] - http://ma= rkmail.org/thread/7pww6veepr77kzuq
[2] - http://axis.apache.org/axis2/java/core/api/org/apache/axis2/jaxws/= marshaller/MethodMarshaller.html

Thanks ! =A0 =A0 =A0 =A0 =A0
=A0


Thanks in advance


Dan= ushka Seneviratne=A0





--
Sagara Gunathunga
Blog =A0 =A0 =A0- http://ssagara.blogspot.com
Web =A0 =A0 =A0- http://people.apache.org/~sagar= a/
LinkedIn - http://www.linkedin.com/in/ssagara --0015173fedfac368d804da3e28a6--