This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes Web Services and the fly likes Compatibility issue between Axis2 JAXWS service and Axis1.x client Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Compatibility issue between Axis2 JAXWS service and Axis1.x client" Watch "Compatibility issue between Axis2 JAXWS service and Axis1.x client" New topic
Author

Compatibility issue between Axis2 JAXWS service and Axis1.x client

John Spartan
Greenhorn

Joined: Oct 18, 2012
Posts: 1
Hello,

We have an Axis2 JAXWS service which is consumed by JAXWS clients as well as Axis1.x clients(JAXRPC).

The parameter names generated by our web service have arg0 etc. But when the Axis1.x clients use the same WSDL and send a message, we do not get parameters as arg0 but instead we get them as the request object name.

The request message in the service implementation class is fine in case of JAXWS client but it is Null in case of Axis1.x client.

The same web service used to work fine on Websphere 6. But recently we migrated to Websphere 8 and it started failing. We cannot ask clients to modify.

Any thoughts?

J
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: Compatibility issue between Axis2 JAXWS service and Axis1.x client
 
Similar Threads
SOAP with Attachments (SwA) with Axis2, problem.
is it possible for Axis2 and Axis1 co-exist in client application?
my webservice supports Axis1.x but not Axis2.x ,so is it the compatibility issue?
accessing attribute value from response
my webservice supports Axis1.x but not Axis2.x ,so is it the compatibility issue?