Deepal,
I agree that an isComplete method is convinient, but it can be easily added
as I have shown in the example.
So it's not a major issue.
Perhaps if we document the behaviour properly we don't really need to add
that method in a hurry.
But I also agree that for the sake of backward compatibility it is good to
add that method.
It will also allow an easy migration path to the users.
Regards,
Rajith
On 10/8/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
>
> Hi Huitang ,
> Yes I also agree with you that is one of the missing API in the
> AxisCallback , and even I have found it difficult without that. So
> please create a JIRA I am more than happy to fix that , though it is
> going to be a API changes.
>
> Thanks
> Deepal
> > 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]
>
>
