axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From TimDog <>
Subject Differences between Axis 1.4 and Axis2 client generation
Date Mon, 08 Oct 2007 18:34:55 GMT

I'm using Axis2 to generate the  WSDL for my service...and I have a nagging
question in the back of my mind.

Why are clients generated by the Axis2 wsdl2java (the default adb) of the

stub.function(FunctionObj obj)

And the clients generated from the Axis1.4 wsdl2java of the form

stub.function(param1, param2, param3)


Is there a way to make the Axis2 wsdl2java produce a stub that I can just
call methods and parameters like the 1.4 clients instead of messing around
with all of this object indirection?  

It seems(to me) that should be added to the client stub automatically,
because we're doing all of that coding over and over again and it's
encapsulated fairly easily.  

///The Axis 1.4 Client

SoapBindingStub stub;
		try {
			stub = (SoapBindingStub)
			new ISoapBindingStubServiceServiceLocator().getsoapbindingstub(new
			 Object resultObj = stub.function(param1, param2, param3);
		catch (javax.xml.rpc.ServiceException jre) {
		catch (RemoteException e) {
		} catch (MalformedURLException e) {

The Axis2 Client
SoapBindingStub stub;
		try {
			stub = (SoapBindingStub)
			new SoapBindingStub(test.getServiceUrl());
                        SoapBindingStub.FunctionObj functionObj = new
		        SoapBindingStub.FunctionResponseObj responseObj =
                        Object resultObj = responseObj.getReturn();

		catch(Exception e){
			System.err.println("Service Loaded");
View this message in context:
Sent from the Axis - User mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message