Hi Frank,
Forgot to mention. Dispatching will consider the namespace of the SOAP
body's first element too in its evaluation if it has no alternative in
locating an operation.
Regards,
Senaka
> Hi Frank,
>
> Since you are using SOAP, the Server will dispatch (recognize the
> service/operation) fr
Hi Frank,
Since you are using SOAP, the Server will dispatch (recognize the
service/operation) from the request in the following manner.
1. Using the request URI,
http://my_host:my_port/axis2/services/my_service/my_operation
Your URI must have the format above. my_port can be optional, and http
Frank Zhou wrote:
Hi Senaka,
I just tried the API
axis2_svc_client_send_receive(_wsf_service_client,_env,
payload) and it works. So that means I don't have to
set the operation for the client call? How does the
server know which operation to perform then?
The information of what method to
Hi Senaka,
I just tried the API
axis2_svc_client_send_receive(_wsf_service_client,_env,
payload) and it works. So that means I don't have to
set the operation for the client call? How does the
server know which operation to perform then?
I used axis-j for sometime, I remember that to prepare
a c
Hi Frank,
We do have several working samples that are shipped with each distribution
and is also available on the svn head.
Please check inside the samples directory for an echo sample. I hope that
might solve your issue.
If not, you simply can call this method.
node = axis2_svc_client_send_rec
Hi, All,
I am trying to set up a web service client using
AXIS2/c. I was able to compile the source code and
call APIs in my C++ application. However, it seems
that I made some mistakes in setting up the client
properly, so that when I try to send a request, I
always get NULL response. I debugged
