aspose file tools*
The moose likes Web Services and the fly likes Axis2 1.5 Asynchronous  Non Blocking Client Callback not working Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Axis2 1.5 Asynchronous  Non Blocking Client Callback not working" Watch "Axis2 1.5 Asynchronous  Non Blocking Client Callback not working" New topic
Author

Axis2 1.5 Asynchronous Non Blocking Client Callback not working

Mat Anthony
Ranch Hand

Joined: May 21, 2008
Posts: 237
Hi All,
I'm trying to get a client to work asynchronous with a webservice. The client sucesfully calls the service, but the client call back handler never gets invoked once the webservice has completed the clients request.
Both the client and the server have been built using Axis2 1.5. In the WSDL2Java I have included the -a argument to generate asynchronous code.
The return response from the web service via the soap engine should go to method receiveResultSportDetails that overrides the autogenerated method in abstarct class WebServiceCallbackHandler.

I have got no idea how to get this working.

Code used to generate Client and web service


Client Code


Mat Anthony
Ranch Hand

Joined: May 21, 2008
Posts: 237
Hi All,
if I comment out the following line then the callBackHandler is called. By default UseSeparateListener is set to false, indicating that the soap request and response are sent over the same
channel. If you set it to true then the request and response are over separate channels, hence better since the original channel is not left open, especialy if the web service has to process
a lot of data and will take along time to respond. The client callBackHandler is never called if setUseSeparateListener is set to true.


I'm currently using Oracle 10g oc4j application server to host the webservice. I'm not sure about the following:-
1) If the client has to provide a replyTo


2) The port the client will be listening on.

Searching the web I found that I had to add the floowing line to services.xml
Used when a replyTo header is found in the soap header, from the client.


I have also added addressing-1.5.6.jar and soamonitor-1.5.6.jar to the classpath.

Can anybody help
Mat Anthony
Ranch Hand

Joined: May 21, 2008
Posts: 237
Hi All,
It looks like axis2 soap engine does not recognise the ReplyTo address in the request soap header, if I set the UseSeparateListener to true.
Has anybody managed to get this working using axis2 1.5?

Mat
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Axis2 1.5 Asynchronous Non Blocking Client Callback not working