On 8/23/07, Giorgio Zoppi <[EMAIL PROTECTED]> wrote:
>
> 2007/8/23, Simon Laws <[EMAIL PROTECTED]>:
> > On 8/23/07, Simon Nash <[EMAIL PROTECTED]> wrote:
> > >
> > > Giorgio,
> > > This is supported and working for both the local SCA binding and the
> > > Web Service binding. The supportsAsyncOneWayInvocation=false setting
> > > means that the binding doesn't provide this support internally, so the
> > > core invocation framework adds a nonblocking interceptor that does a
> > > thread switch. It appears that you are using the distributed
> > > SCA binding over Web services (is that correct?) so there could be an
> > > issue with this binding. Bindings that can support async invocations
> > > internally are supposed to set the flag to true rather than false,
> > > and I'd expect the distributed SCA binding to fall into that category.
> > >
> > > Simon
> >
> > > Hi Jo
> >
> > I'm fixing up the remote callbacks for the sca binding now. They should
> > already work for the local case and explicit web services bindings (see
> > samples/simple-callback and samples/simple-callback-ws) It needs
> changing
> > in the sca binding case now that raymond has changed the way that the
> > wires/invocation chains are created. If you want to make progress with
> > you're sample right now you could switch to the explicit web services
> > binding for the time being. Otherwise the fix should be done in an hour
> or
> > so (I hope:-)
> >
> > With one way invocations you've found something I haven't tried with the
> > default binding in remote mode. It's just using the web services binding
> > under the covers so there's no reason why it shouldn't work but I expect
> > there is some coding error. If you've got some thoughts here about
> what's
> > going wrong that would would good.
>
> Ok. Thank you very much. I'll try and debug it.
> Cheers,
> Jo.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> Hi
I've put in some fixes now for callbacks across the remote version of the
sca binding and for @OneWay interfaces. There are a couple more simple test
cases to cover this in the binding-sca-axis2 module. In the one way case I
just replaced the line you identified with...
public boolean supportsAsyncOneWayInvocation() {
if (isTargetRemote()) {
return distributedProvider.supportsAsyncOneWayInvocation();
} else {
return false;
}
}
The isTargetRemote call needs some caching applied to it as it gets used in
various places but the basic function is working. The changes are checked
into trunk in svn now.
Regards
Simon
