Thanks for your input. I saw the thread you mentioned before I sent out
my question to the list. However, I cannot see the solution to the
question. The main thread can be finished before the spawning thread
finishes getting the response from the web service server. Also, in
axis2 1.3 sample codes, it still uses the old Callback class.
I just wonder how the main thread can detect whether the spawning thread
is complete or not with the new AxisCallback API.
Any idea?
Suran Jayathilaka wrote:
Huitang Li wrote:
Hi,
I created a web service client following Async/One Channel model
using axis2-generated stub. In the stub code, AxisCallback interface
is used.
For almost all tests, no soap message response is received before the
client is finished. This is verified with the help of the excellent
tool tcpmon.
In AxisCallback, I did not see something like isComplete() to test
whether a whole message is retrieved or not. So I had to replace the
AxisCallback with the depreciated Callback, and then put the
following code in the stub.
while (!callback.isComplete()) {
Thread.sleep(1000);
}
Does anyone have a better solution without having to use the
deprecated API?
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi!
Please refer to this thread.
http://www.mail-archive.com/[email protected]/msg31442.html
Cheers.
Suran
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
