• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Axis Vs Axis2

 
Ranch Hand
Posts: 59
Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Everyone,

Can anyone tell me what is the difference between the Axis and Axis2, in terms of Efforts required to generate the webservice client, means I have the WSDL, I have to create the client for this web service.
Mainly, I have to migrate from AXIS to AXIS2 please assist in this.

Regards,
 
Ranch Hand
Posts: 129
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Some differences I found between Axis and Axis2

1.
According to the WSDL file generated by Axis and Axis2
Axis uses RPC message style and Axis2 uses document message style by default.

2.
The Java Stub classes generated by Axis' WSDL2Java tool make sense with what
I learn from RMH book.
However, the Java Stub classes generated by Axis2's WSDL2Java tool are quite different from Axis'
Besides, I got error when I try to run those Java Stub classes.
 
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Axis 1 supports the JAX-RPC API (amongst others), while Axis 2 supports JAX-WS (amongst others). So if your service uses JAX-RPC, you're in for some rework.
 
Ranch Hand
Posts: 2187
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Axis is pretty stable and easy to learn. Best bet is to learn Axis good, and then start to look at Axis2. You will see what I mean.

Good luck!
[ November 12, 2008: Message edited by: James Clark ]
 
Rizwan Patel
Ranch Hand
Posts: 59
Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ulf,

Axis 1 supports the JAX-RPC API (amongst others), while Axis 2 supports JAX-WS (amongst others). So if your service uses JAX-RPC, you're in for some rework.



I have previously working webservice in Axis all the Stubs and necessary clients are created for that working webservice. Now as to upgrade to support the additional functionality which is being provided in Axis2 with the help of "XMLBeans" databinding, Which can tolerate the change in the incoming request message such as When in an input request message's object three part are present and we can give the values for the two parts and the third part is alloted to the default value and our webservice get invoked and full fill the request.
In this activity, I think all the stub structure will be change as previously in old version it generating the Locater class, stub and other supporting classes. So i wanted to know whether the same client written previously will work for the new updated environment. or I should have to write the new client by completely reworking on that.
Please help me to understand this gotcha.
 
I'm not dead! I feel happy! I'd like to go for a walk! I'll even read a tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic