Solution Hacker » axis http://www.solutionhacker.com This blog provides solutions for enterpreneurs! Sun, 05 Feb 2012 00:45:27 +0000 en hourly 1 http://wordpress.org/?v=309 This blog provides solutions for enterpreneurs! Solution Hacker no This blog provides solutions for enterpreneurs! Solution Hacker » axis http://www.solutionhacker.com/wp-content/plugins/powerpress/rss_default.jpg http://www.solutionhacker.com Axis2 vs XFire http://www.solutionhacker.com/implement-your-idea/design/axis2-vs-xfire/ http://www.solutionhacker.com/implement-your-idea/design/axis2-vs-xfire/#comments Thu, 06 Dec 2007 19:36:51 +0000 admin http://www.solutionhacker.com/2007/12/06/axis2-vs-xfire/ Recently, I have assigned a web service project to one of my developers. To provide a guideline to choose the stack, I need to look into the solution provided by Axis and XFire again. Previously, it is no brainer in favor of XFire because Axis 1 is using DOM based parser whereas XFire is using StAX. Now, Axis 2 has come out that uses StAX parser as well. After a series of benchmark comparison and arguments from both parties. I feel that picking either framework isn't likely to matter much. And if it does matter, make sure you chose the proper databinding toolkit as that will have the biggest affect on your performance.

For XFire, it uses JAXB for databinding by default that you are replaced with JiBX. Why JiBX is faster? The reason is JAXB uses reflection to populate the bean whereas JiBX uses byte code generation. According to Dan, JiBX has significant performance improvements. JiBX can provide significant performance improvements over JAXB as it does not use reflection, but instead does byte code generation to optimize databinding - Dan

For Axis2, it creates its own databinding solution named ADB and it is comparable with JiBX. So, Axis2 really has caught up its competitors in term of performance. Whether I will switch to use Axis2. Probably not. Because I don't see it worth the hassle to learn another databinding solution and WS framework that gives you practically the same thing that XFire already provided. By switching to a StAX based framework you're likely to see something like a 3-5x speedup (or something like 30x if you switch from rpc/encoded to doc/literal as well). This can make a significant difference in your application's responsiveness and load handling. As long as you are using StAX, you are good. Oh, before I forget. For anyone who is using XFire or attempt to use XFire, please look at Apache CXF. According to XFire, CXF is XFire 2.0. I am excited to see those new features from CXF:

  1. Spring 2.0 XML support
  2. RESTful service support
  3. JSON support
  4. And some of WS specs support as well

Here is what I found from XFire site: We encourage all users who are currently evaluating XFire to use CXF instead at this point. If you are already an XFire user, you may wish to consider migrating to CXF depending on where you are in your own release cycle. We will continue to support XFire in the future with bug fix releases, but feature development will be focused on CXF. * UPDATE * 12/6/2007: Apache CXF 2.0 currently doesn't support JiBX. It is expecting to support it for CXF 2.1. Reference http://www.infoq.com/news/2007/02/axis2-xfire-benchmark

]]> Recently, I have assigned a web service project to one of my developers. To provide a guideline to choose the stack, I need to look into the solution provided by Axis and XFire again. Previously, it is no brainer in favor of XFire because Axis 1 is using DOM based parser whereas XFire is using StAX. Now, Axis 2 has come out that uses StAX parser as well. After a series of benchmark comparison and arguments from both parties. I feel that picking either framework isn’t likely to matter much. And if it does matter, make sure you chose the proper databinding toolkit as that will have the biggest affect on your performance.

For XFire, it uses JAXB for databinding by default that you are replaced with JiBX. Why JiBX is faster? The reason is JAXB uses reflection to populate the bean whereas JiBX uses byte code generation. According to Dan, JiBX has significant performance improvements. [code]]czoyMjA6XCIgSmlCWCBjYW4gcHJvdmlkZSBzaWduaWZpY2FudCBwZXJmb3JtYW5jZSBpbXByb3ZlbWVudHMgb3ZlciBKQVhCIGFzIGl7WyYqJl19dCBkb2VzIG5vdCB1c2UgcmVmbGVjdGlvbiwgYnV0IGluc3RlYWQgZG9lcyBieXRlIGNvZGUgZ2VuZXJhdGlvbiB0byBvcHRpbWl6ZXtbJiomXX0gZGF0YWJpbmRpbmcgLSA8YSBocmVmPVwiaHR0cDovL25ldHpvb2lkLmNvbS9ibG9nL1wiIHRhcmdldD1cIl9ibGFua1wiPkRhbjwvYT4gXCJ7WyYqJl19O3tbJiomXX0=[[/code]

For Axis2, it creates its own databinding solution named ADB and it is comparable with JiBX. So, Axis2 really has caught up its competitors in term of performance. Whether I will switch to use Axis2. Probably not. Because I don't see it worth the hassle to learn another databinding solution and WS framework that gives you practically the same thing that XFire already provided. By switching to a StAX based framework you're likely to see something like a 3-5x speedup (or something like 30x if you switch from rpc/encoded to doc/literal as well). This can make a significant difference in your application's responsiveness and load handling. As long as you are using StAX, you are good. Oh, before I forget. For anyone who is using XFire or attempt to use XFire, please look at Apache CXF. According to XFire, CXF is XFire 2.0. I am excited to see those new features from CXF:

  1. Spring 2.0 XML support
  2. RESTful service support
  3. JSON support
  4. And some of WS specs support as well

Here is what I found from XFire site: We encourage all users who are currently evaluating XFire to use CXF instead at this point. If you are already an XFire user, you may wish to consider migrating to CXF depending on where you are in your own release cycle. We will continue to support XFire in the future with bug fix releases, but feature development will be focused on CXF. * UPDATE * 12/6/2007: Apache CXF 2.0 currently doesn't support JiBX. It is expecting to support it for CXF 2.1. Reference http://www.infoq.com/news/2007/02/axis2-xfire-benchmark

]]> http://www.solutionhacker.com/implement-your-idea/design/axis2-vs-xfire/feed/ 0