Hi Gordonw,
Axis2 server side use several criteria to dispatch incoming messages,
"soapAction" is one of them take a look [1]. In fact soapAction is
mandatory in SOAP 1.1 but replaced in SOAP 1.2 using a optional "action". So
your client can send one of above input data according to underline
dispatching approach.
You can make operation name part of the EPR as follows.
ServiceClient sender = new ServiceClient();
Options options = new Options();
options.setTo(new EndpointReference("http://host/MyService/MyOperation";));
sender.setOptions(options);
[1] - http://wso2.org/library/176
Thanks !
On Thu, Mar 3, 2011 at 5:21 AM, Gordon Brown <[email protected]>wrote:
> Hi All,
>
> I am using axis2/java to build a web service client component. I have a
> question.
>
> Is there a way to set the operation name in the web service client?
>
> Using axis/j, I can do something like this:
>
> org.apache.axis.client.Service soapService = new
> org.apache.axis.client.Service();
> soapService.createCall();
> call = soapService.getCall();
> call.setTargetEndpointAddress(soapAddress);
>
> //setting operation name in the call object
> call.setOperationName(new QName(operationNamespace,
> operationName));
>
> call.setSOAPActionURI(soapAction);
> call.setPortName(new QName(portNamespaceURI,portName));
>
> But in axis2/java, I don't see how I can set the operation name in the
> service client. I got an exception when trying to do this:
>
> ServiceClient serviceClient = new ServiceClient();
>
> //The following line get an exception, try to set operation name in
> the service client
> OperationClient operationClient = serviceClient.createClient(new
> QName(operationNamespace, operationName));
>
> operationClient.getOptions().setAction(soapAction);
> operationClient.getOptions().setTo(new
> EndpointReference(soapAddress));
>
> operationClient.getOptions().setExceptionToBeThrownOnSOAPFault(true);
>
> operationClient.getOptions().setTransportInProtocol(Constants.TRANSPORT_HTTP);
> I understand that the server side might not need the operation name, it can
> use soapAction et cetera to figure out where to dispatch the message. But
> how about the client doesn't know the soapAction (it might not even have
> one), all it know is the operation name, in which case the server will have
> to rely on the operation name (as the last resort), right?
>
> Your help is much appreciated.
> Gordon
>
>
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
