Hi,
Just my two cents as an AXIS2 user.AXIS2 does a much better job at performance based on our tests(especially ADB) - We nearly improved 50% with AXIS2 webservice as compared to AXIS1 webservice. ADB is very fast but does not seem very mature at least to me, we had generated some code but had to fix by hand. (This is in the latest version of AXIS2) However the generated code is so simple that you can get your hands dirty very quickly. Some more issues we faced were with the way XS:any type is handled in AXIS2. We were using some XML signatures API and it simply rejected the reframed message from the AXIS/xmlbeans API. Still investigating if we are doing something wrong. I think AXIS1 was doing a better job of handling the xs:any schema types. Regards, Chandan _____ From: Gaurav Lall [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 08, 2008 5:02 PM To: [email protected] Subject: Re: [General] Advantages of Axis2 over Axis1 This might be helpful http://wiki.apache.org/ws/StackComparison 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <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: [EMAIL PROTECTED] To: [email protected] <mailto:[email protected]> 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 <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> 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! <http://www.windowslive.com/?ocid=TXT_TAGHM_Wave2_powerofwindows_012008>
