Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 59585 invoked from network); 8 Jan 2008 20:36:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Jan 2008 20:36:43 -0000 Received: (qmail 77515 invoked by uid 500); 8 Jan 2008 20:36:20 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 77500 invoked by uid 500); 8 Jan 2008 20:36:20 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 77481 invoked by uid 99); 8 Jan 2008 20:36:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jan 2008 12:36:20 -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 (athena.apache.org: domain of subir.sasikumar@gmail.com designates 64.233.178.242 as permitted sender) Received: from [64.233.178.242] (HELO hs-out-2122.google.com) (64.233.178.242) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jan 2008 20:35:51 +0000 Received: by hs-out-2122.google.com with SMTP id l65so6173753hsc.0 for ; Tue, 08 Jan 2008 12:35:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=T6lT/9jAM/LFaAwCVbmyB0dm8xlTfGBsJ8XO+yZSEdg=; b=TqEn6/TYXZKIAO9yzrCu/Xd9eo7r9FVoi+gk/vMUuW8gVEgnmgl6A5CTFxqegbgyN/T2YlnPSjTAo7RPa+YSYjBclccoFmn9ylt+NyF0xZVhU0C+iQTuWjDgnr9Tf1TeOR1Z8odpW7lYW4cNjr5pAtk4r6ilX9hcYo1JSvHl03E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=khKWB2cD7rS3LBC42dmQG5Ghi61S1T/kicct0hOA3HjPcV/PbMPxQR0LCMlqLzFxC8HZ/IYjmhAR6tcGrCjCrb3d+sTGo2w0OxyDP2OMpgGKMW5NJKr/CyvS7uzK77QQktsn9D9BUkDYuC4UppWVThpwh/DklPvAzKd82CDYCoE= Received: by 10.143.33.19 with SMTP id l19mr549375wfj.85.1199824555267; Tue, 08 Jan 2008 12:35:55 -0800 (PST) Received: by 10.142.125.13 with HTTP; Tue, 8 Jan 2008 12:35:55 -0800 (PST) Message-ID: <459e88fc0801081235y7864bac0s60318123f041ee7b@mail.gmail.com> Date: Tue, 8 Jan 2008 22:35:55 +0200 From: "Subir S" To: axis-user@ws.apache.org Subject: Re: [General] Advantages of Axis2 over Axis1 In-Reply-To: <47835F19.505@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_31290_26223555.1199824555272" References: <459e88fc0801060139q7c7a4d20pe97e5c8f926ff1d5@mail.gmail.com> <459e88fc0801070725r4d10ed8esd3b7c250e42233ca@mail.gmail.com> <47835F19.505@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_31290_26223555.1199824555272 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 1/8/08, Gaurav Lall wrote: > This might be helpful > http://wiki.apache.org/ws/StackComparison > Thanks Gaurav!!. By chance do you know which stable release of Axis2 is being referred in this webpage for comparison? > Subir S wrote: > > Thanks for the replies Martin and Gaurav. > > Does any one know if Axis2 has full support for JAX-WS 2.0 and the latest > JAXB spec? > Infact it was mentioned in one of the performance benchmark article that > JAXB is only experimental in Axis2? > > Why has Axis2 relied on ADB, when there are these other standard data > bindings available. Especially i think JAXB should be a widely accepted > one!! > > Any thoughts? Some links which throw some light on this? > > Subir > > > On 1/7/08, gaurav lall wrote: > > > > What I like about Axis2 is the > > > > Simplicity of API in terms of invoking the service and writing the > > service code > > Support for different data binding technologies > > > > Thanks > > Gaurav > > On Jan 6, 2008 9:15 AM, Martin Gainty wrote: > > > > > Good Point > > > > > > The main feature of Axis2 is an architectural re-design to truly > > > implement AOP > > > features which would be shared by multiple services are refactored to > > > modules > > > The modules then are engaged to the implemented service > > > > > > another improvement is asynchronous method invocation > > > http://ws.apache.org/axis2/1_3/migration.html > > > > > > Included are transport independence so converting from HTTP to FTP > > > is achieved declaratively instead of programmatic > > > > > > The Axis1 engine was essentially a SAX parser ..AXIS2 is essentially a > > > Stax parser > > > > > > Anyone else? > > > Martin > > > > > > ______________________________________________ > > > Disclaimer and confidentiality note > > > Everything in this e-mail and any attachments relates to the official > > > business of Sender. This transmission is of a confidential nature and Sender > > > does not endorse distribution to any party other than intended recipient. > > > Sender does not necessarily endorse content contained within this > > > transmission. > > > > > > > > > > > > ------------------------------ > > > Date: Sun, 6 Jan 2008 11:39:06 +0200 > > > From: subir.sasikumar@gmail.com > > > To: axis-user@ws.apache.org > > > Subject: [General] Advantages of Axis2 over Axis1 > > > > > > Hi All, > > > > > > Any help or advise is appreciated. > > > > > > I want to convince our project to move from Axis1 rpc-enc WS to Axis2 > > > (either rpc-lit / doc-lit). > > > Also i am preparing a document to highlight them. > > > My initial study from various internet resources have told me about > > > these > > > a.) more performance for Axis2. (Benchmark results between Apache > > > Axis1 and Apache Axis2 http://wso2.org/library/91 ) > > > b.) considerable performance over other WS applications (Benchmark > > > results between Apache Axis2 and Codehaus XFire > > > http://wso2.org/library/588 ) > > > c.) Another stuff we use rpc-encoded services. But this I can change > > > in Axis1 also to doc-lit or rpc-lit to make it inline with WS-I basic > > > profile. > > > > > > I also saw various WS-* specification support that Axis2 has. But is > > > there some thing much more significant in Axis2 which has a cutting edge > > > over Axis1. Some reference to such comparisons over the web would be higly > > > helpful. > > > Thanks in advance. > > > > > > Regards > > > Subir > > > > > > > > > > > > ------------------------------ > > > Get the power of Windows + Web with the new Windows Live. Get it now! > > > > > > > > > > > > ------=_Part_31290_26223555.1199824555272 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 1/8/08, Gaurav Lall <learnframeworks@gmail.com> wrote:
 
Thanks Gaurav!!. By chance do you know which stable release of Axis2 is being referred in this webpage for comparison?

 
Subir S wrote:
Thanks for the replies Martin and Gaurav.
 
Does any one know if Axis2 has full support for JAX-WS 2.0 and the latest JAXB spec?
Infact it was mentioned in one of the performance benchmark article that JAXB is only experimental in Axis2?
 
Why has Axis2 relied on ADB, when there are these other standard data bindings available. Especially i think JAXB should be a widely accepted one!!
 
Any thoughts? Some links which throw some light on this?
 
Subir

 
On 1/7/08, gaurav lall <learnframeworks@gmail.com > wrote:
What I like about Axis2 is the

Simplicity of API in terms of invoking the service and writing the service code
Support for different data binding technologies

Thanks
Gaurav

On Jan 6, 2008 9:15 AM, Martin Gainty <mgainty@hotmail.com> wrote:
Good Point
 
The main feature of Axis2 is an architectural re-design to truly implement AOP
features which would be shared by multiple services are refactored to modules
The modules then are engaged to the implemented service

another improvement is asynchronous method invocation
http://ws.apache.org/axis2/1_3/migration.html

Included are transport independence so converting from HTTP to FTP is achieved declaratively instead of programmatic
 
The Axis1 engine was essentially a SAX parser ..AXIS2 is essentially a Stax parser

Anyone else?
Martin

______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.



Date: Sun, 6 Jan 2008 11:39:06 +0200
From: subir.sasikumar@gmail.com
To: axis-user@ws.apache.org
Subject: [General] Advantages of Axis2 over Axis1


Hi All,
 
Any help or advise is appreciated.
 
I want to convince our project to move from Axis1 rpc-enc WS to Axis2 (either rpc-lit / doc-lit).
Also i am preparing a document to highlight them.
My initial study from various internet resources have told me about these
a.) more performance for Axis2. (Benchmark results between Apache Axis1 and Apache Axis2 http://wso2.org/library/91 )
b.) considerable performance over other WS applications (Benchmark results between Apache Axis2 and Codehaus XFire http://wso2.org/library/588 )
c.) Another stuff we use rpc-encoded services. But this I can change in Axis1 also to doc-lit or rpc-lit to make it inline with WS-I basic profile.
 
I also saw various WS-* specification support that Axis2 has. But is there some thing much more significant in Axis2 which has a cutting edge over Axis1. Some reference to such comparisons over the web would be higly helpful.
Thanks in advance.
 
Regards
Subir
 

Get the power of Windows + Web with the new Windows Live. Get it now!




------=_Part_31290_26223555.1199824555272--