As mentioned in my previous post, it looks like a bug
http://issues.apache.org/jira/browse/AXIS2-3265
There is nothing wrong with the wsdl. I am using resin 3.1.3 as the
server. Probably this is something related to the xmlStreamReader
implemented by resin? Right now I have no time to verify t
On 10/12/07, Huitang Li <[EMAIL PROTECTED]> wrote:
>
>
> With further debugging, I found something interesting: when the
> onMessage() method is done in AxisCallback, the application proceeds on
> the method "public void run() " in class OutInAxisOperationClient, and
> then somehow the application
It looks like I am hitting the same bug as
http://issues.apache.org/jira/browse/AXIS2-3265
Any solution?
Thanks.
Huitang Li wrote:
I mean the run() method in the private class
NonBlockingInvocationWorker in class OutInAxisOperationClient.
private class NonBlockingInvocationWorker implem
I mean the run() method in the private class NonBlockingInvocationWorker
in class OutInAxisOperationClient.
private class NonBlockingInvocationWorker implements java.lang.Runnable{
private org.apache.axis2.client.async.Callback callback;
private org.apache.axis2.context.MessageC
With further debugging, I found something interesting: when the
onMessage() method is done in AxisCallback, the application proceeds on
the method "public void run() " in class OutInAxisOperationClient, and
then somehow the application seems hanging for ever.
I have not downloaded the axis2
Put you notification logic in the
public void onComplete() {
//nothing here
}
So when it completes (either fault/error or sucess) , this method will be
called.
Here is a faily elementry example (not the most elegant)
Modify the generated class as follows.
public vo
Thanks, Deepal. I will be happy to create a JRIA. But can you show me a
good example using this new API in the client code? I am working on a
project, and I cannot wait for the next Axis2 release.
Thanks.
Huitang
Deepal jayasinghe wrote:
Hi Huitang ,
Definitely a bug in codegen , please cr
Hi Huitang ,
Definitely a bug in codegen , please create a JRIA.
Thanks
Deepal
> All these codes are auto-generated by Axis2 1.3 wsdl2java command. I
> do not know whether it is an old callback or not. But it does says:
>
> _operationClient.setCallback(new
> org.apache.axis2.client.async.AxisCallb
All these codes are auto-generated by Axis2 1.3 wsdl2java command. I do
not know whether it is an old callback or not. But it does says:
_operationClient.setCallback(new
org.apache.axis2.client.async.AxisCallback() {
// all the codes that I pasted in my previous email.
}
In the generated code
What do you mean by the "application is stuck" ? How does your application
figure out if a response is received?
Can you please cut paste the code that uses the AxisCallback.
Does the onMessage, onError or onFault methods get called?
If so why do u say it is stuck?
Looks like the onMessage and on
I used Axis2-generated adb client with a little modification. In the
client, the generated code uses AxisCallback. I think that is very
common piece of code in Axis2-generated ADB client. Because the
application stuck, I replaced AxisCallback object with an Callback
object, and it works fine.
How did u use it?
Can you cut paste the code here.
Regards,
Rajith Attapattu
Red Hat.
On 10/11/07, Huitang Li <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> When I use the new API AxisCallback, the application seems stuck, and it
> is taking forever to get any response. However, when I switched to the
>
Hi,
When I use the new API AxisCallback, the application seems stuck, and it
is taking forever to get any response. However, when I switched to the
Callback class, I got the response from web service quickly.
Any idea?
Thanks.
-
13 matches
Mail list logo
