You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org> on 2007/11/13 09:27:51 UTC

[jira] Resolved: (AXIS2-3272) wsdl2java created stub class: AxisCallback interface not properly implemented

     [ https://issues.apache.org/jira/browse/AXIS2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amila Chinthaka Suriarachchi resolved AXIS2-3272.
-------------------------------------------------

    Resolution: Invalid

we don't have to do any manadatory thing in onComplete method. It is just called after the client processing is finished.
Recently I tested the Asynchronus method with MS wcf end points and that worked fine. So seems to be that the bug is already closed.

> wsdl2java created stub class: AxisCallback interface not properly implemented
> -----------------------------------------------------------------------------
>
>                 Key: AXIS2-3272
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3272
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: codegen
>    Affects Versions: 1.3
>         Environment: windows
>            Reporter: Huitang Li
>            Assignee: Amila Chinthaka Suriarachchi
>
> The wsdl2java-generated stub code implements AxisCallback. However, the onComplete() method is blank, which is the probable cause of application hanging.
> Please see the communication in the axis-users mailing list pasted below:
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 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.AxisCallback() {
> > > // all the codes that I pasted in my previous email.
> > > }
> > >
> > > In the generated code, the onComplete() method looks like this:
> > >
> > > public void onComplete() {
> > >                    // Do nothing by default
> > >                }
> > >
> > >
> > > Maybe there is something incorrectly generated by wsdl2java?
> > >
> > >
> > >
> > >
> > > Rajith Attapattu wrote:
> >> >> 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 onError methods get called, bcos u seem
> >> >> to have put the old callback there and you mentioned that it works.
> >> >>  
> >> >>
> >> >>                 public void onComplete() {
> >> >>                     //nothing here
> >> >>                 }
> >> >>
> >> >>
> >> >> I also see that the onComplete method is empty.
> >> >>
> >> >> -- 
> >> >> Rajith Attapattu
> >> >> Red Hat
> >> >> Blog http://mutlix.blogspot.com/ 
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-user-help@ws.apache.org
> > >
> > >
> -- Thanks, Deepal ................................................................ "The highest tower is built one brick at a time"  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org