You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Subir S <su...@gmail.com> on 2008/01/06 10:39:06 UTC
[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
Re: [General] Advantages of Axis2 over Axis1
Posted by Subir S <su...@gmail.com>.
>>>Included are transport independence so converting from HTTP to FTP
is achieved declaratively instead of programmatic
Martin, i did not get this one? Could you please throw some light..some more
light :-)
Subir
On 1/6/08, Martin Gainty <mg...@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!<http://www.windowslive.com/?ocid=TXT_TAGHM_Wave2_powerofwindows_012008>
>
Re: [General] Advantages of Axis2 over Axis1
Posted by Subir S <su...@gmail.com>.
On 1/8/08, Chandan Gupta <ch...@impetus.co.in> wrote:
> 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.
>
Chandan, out of curiosity. Did you try with ADB alone? I mean did you try
the other data bindings also and then concluded that ADB was quick enough
for you?
> 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:learnframeworks@gmail.com]
> *Sent:* Tuesday, January 08, 2008 5:02 PM
> *To:* axis-user@ws.apache.org
> *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* <le...@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 <mg...@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!
> <http://www.windowslive.com/?ocid=TXT_TAGHM_Wave2_powerofwindows_012008>
>
>
>
>
>
>
>
Re: [General] Advantages of Axis2 over Axis1
Posted by Amila Suriarachchi <am...@gmail.com>.
On Jan 8, 2008 6:10 PM, Chandan Gupta <ch...@impetus.co.in> wrote:
> 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.
>
I agree with you that ADB does not provide 100% schema support. After axis2
1.3 release I have fixed lot of issues with ADB. if you could please test
this with a nighly build and report any remaining issues. If it is an simple
fix or an problem with a supporting schema construct I can fix them for
Axis2 1.4 which is due to release end of February.
>
>
> 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:learnframeworks@gmail.com]
> *Sent:* Tuesday, January 08, 2008 5:02 PM
> *To:* axis-user@ws.apache.org
> *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* <le...@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 <mg...@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!
> <http://www.windowslive.com/?ocid=TXT_TAGHM_Wave2_powerofwindows_012008>
>
>
>
>
>
>
>
--
Amila Suriarachchi,
WSO2 Inc.
RE: [General] Advantages of Axis2 over Axis1
Posted by Chandan Gupta <ch...@impetus.co.in>.
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:learnframeworks@gmail.com]
Sent: Tuesday, January 08, 2008 5:02 PM
To: axis-user@ws.apache.org
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 <le...@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 <mg...@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
<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 <ma...@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 <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>
Re: [General] Advantages of Axis2 over Axis1
Posted by Subir S <su...@gmail.com>.
On 1/8/08, Gaurav Lall <le...@gmail.com> 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 <le...@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 <mg...@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!
> > > <http://www.windowslive.com/?ocid=TXT_TAGHM_Wave2_powerofwindows_012008>
> > >
> >
> >
>
>
Re: [General] Advantages of Axis2 over Axis1
Posted by Gaurav Lall <le...@gmail.com>.
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* <learnframeworks@gmail.com
> <ma...@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
> <ma...@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
> <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
> <ma...@gmail.com>
> To: axis-user@ws.apache.org <ma...@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
> <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!
> <http://www.windowslive.com/?ocid=TXT_TAGHM_Wave2_powerofwindows_012008>
>
>
>
Re: [General] Advantages of Axis2 over Axis1
Posted by Amila Suriarachchi <am...@gmail.com>.
On Jan 8, 2008 7:20 PM, Anne Thomas Manes <at...@gmail.com> wrote:
> ADB is based on StAX and is optimized to work with Axiom (the Axis2
> object model). JAXB is not based on StAX so a bit more work is
> required to make it work with Axiom.
I am not exactly sure about what you mean here. With Axiom you can get the
underline
xml stream reader using the getXMLStreamReaderWithoutCaching() directly. So
for all Axis2 databinding frameworks we send this underline stax reader
directly.
On the serialization side Axis2 use OMDataSource and it has this method.
public void serialize(XMLStreamWriter xmlWriter) throws XMLStreamException{
}
from this method it passes the xmlwriter and to databind framework
serailization logic and Axiom call this
method. So basically any databinding framework dealing with direct
serialization and parsing.
It isn't likely to perform as
> well as ADB, no matter how well it gets optimized.
This is a question I had and I did this performance test in my local
machine. with the wsdl and the request attached using the ab (Apache bench
mark) using 100,000 requests with 4 threads
Axis2 adb 4.570 ms
Axis2 jaxb 8.412ms
Axis2 xmlbeans 8.723ms
CXF jaxb 7.376ms
Comparing Axis2 adb and Axis2 jaxb, ADB is faster and this has a
considerable performance
comparing the CXF jaxb as well.
if you compare Axis2 jaxb performance and CXF jaxb performance the reason
may be what you are saying.
Although we say it parses direct xmlstream reader and writer it may have an
impact on it and the model
CXF use may have reduce this.
But when considering Axis2 adb and jaxb what I thought is this. The
generated jaxb code is a POJO and it
has some annotations on it to help to produce XML. So I think it use some
reflection work at runtime to
figure out the getter and setter method and invoke them.
On the otherhand in ADB it generates the serializing and parse logic and
write it to the bean class it self. (I agree that this make this bean
dirty). But in runtime there is no reflection over head.
This is the main reason I can think of.
Thanks,
Amila.
>
>
> Anne
>
> On Jan 7, 2008 10:25 AM, Subir S <su...@gmail.com> 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 <le...@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 <mg...@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!
> > >
> > >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Amila Suriarachchi,
WSO2 Inc.
Re: [General] Advantages of Axis2 over Axis1
Posted by Anne Thomas Manes <at...@gmail.com>.
ADB is based on StAX and is optimized to work with Axiom (the Axis2
object model). JAXB is not based on StAX so a bit more work is
required to make it work with Axiom. It isn't likely to perform as
well as ADB, no matter how well it gets optimized.
Anne
On Jan 7, 2008 10:25 AM, Subir S <su...@gmail.com> 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 <le...@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 <mg...@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!
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [General] Advantages of Axis2 over Axis1
Posted by Subir S <su...@gmail.com>.
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 <le...@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 <mg...@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!<http://www.windowslive.com/?ocid=TXT_TAGHM_Wave2_powerofwindows_012008>
> >
>
>
Re: [General] Advantages of Axis2 over Axis1
Posted by gaurav lall <le...@gmail.com>.
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 <mg...@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!<http://www.windowslive.com?ocid=TXT_TAGHM_Wave2_powerofwindows_012008>
>
RE: [General] Advantages of Axis2 over Axis1
Posted by Martin Gainty <mg...@hotmail.com>.
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 modulesThe modules then are engaged to the implemented serviceanother improvement is asynchronous method invocationhttp://ws.apache.org/axis2/1_3/migration.htmlIncluded 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 noteEverything 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 +0200From: subir.sasikumar@gmail.comTo: axis-user@ws.apache.orgSubject: [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.
http://www.windowslive.com?ocid=TXT_TAGHM_Wave2_powerofwindows_012008