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 Thilina Gunarathne <cs...@gmail.com> on 2007/06/26 10:06:38 UTC
Re: [axis2] Re: Are we making useSeparateListener "default" if the user has given a replyTo address [was:Re: svn commit: r547986 - in /webservices/axis2/trunk/java/modules: adb/src/org/apache/axis2/rpc/receivers/RPCMessageReceiver.java kernel/src/org
> Think about the case where you set a non anonymous reply to as the
> replyTo address then , what server will do is, will send the response
> to that address. When we do that with our client API , operation client
> will wait to get the response but that will never get it and will be
> timeout.
IMHO if the user is setting a replyTo epr, then he is the person who
should take care of tthese..
>Therefore only way to avoid is to assume if someone set replyTo
> address then he is trying to invoke that using separate channel .
Are we starting a new listener in this case??
Anyway we do not have a control over the replyTo epr given by the
user... It can be a separate endpoint which is already available...
AFAIKS in that case even though we useSeparateListener, our client
side will wait for a response through the listener we setup, which
would never come that way...
I doubt whether this will solve the issue...
Thanks,
Thilina
>
> Thanks
> Deepal
>
> > Can somebody explain the reasons behind the following change...This
> > change went in svn commit: r547986 done by Deepal...
> >
> > Thanks,
> > Thilina
> >
> > On 6/25/07, David Illsley <da...@gmail.com> wrote:
> >> I'd agree that this looks a bit odd and precludes a scenario we were
> >> talking about only last week (setting an anon EPR w/refparams).
> >>
> >> Can someone explain the intention here?
> >> Thanks,
> >> David
> >>
> >> On 23/06/07, Thilina Gunarathne <cs...@gmail.com> wrote:
> >> > Hi,
> >> > > fixing the issue.
> >> > hmm... Fixing which issue :)...
> >> >
> >> >
> >> >webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/description/OutInAxisOperation.java
> >>
> >> > Sat Jun 16 14:24:15 2007
> >> > > @@ -189,6 +189,10 @@
> >> > > useAsync = useAsyncOption.booleanValue();
> >> > > }
> >> > > }
> >> > > + EndpointReference replyTo = mc.getReplyTo();
> >> > > + if(replyTo!=null&&!replyTo.hasAnonymousAddress()){
> >> > > + useAsync = true;
> >> > > + }
> >> > It seems with the above change Axis2 defaults to useSeperateListener
> >> > if a replyTo address is given, even though the user has done just a
> >> > serviceClient.sendReceive(payload);... I doubt whether this is
> >> > correct...
> >> >
> >> > There can be scenerio's where users might already be having a listener
> >> > up and running for the given replyTo address.. In that case trying to
> >> > setup a new listener can give us lot of troubles...
> >> >
> >> > Thanks,
> >> > Thilina
> >> >
> >> >
> >
>
> --
> Thanks,
> Deepal
> ................................................................
> "The highest tower is built one brick at a time"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [axis2] Re: Are we making useSeparateListener "default" if the user has given a replyTo address [was:Re: svn commit: r547986 - in /webservices/axis2/trunk/java/modules: adb/src/org/apache/axis2/rpc/receivers/RPCMessageReceiver.java kernel/src/org
Posted by David Illsley <da...@gmail.com>.
On 26/06/07, Thilina Gunarathne <cs...@gmail.com> wrote:
> > Think about the case where you set a non anonymous reply to as the
> > replyTo address then , what server will do is, will send the response
> > to that address. When we do that with our client API , operation client
> > will wait to get the response but that will never get it and will be
> > timeout.
> IMHO if the user is setting a replyTo epr, then he is the person who
> should take care of tthese..
> >Therefore only way to avoid is to assume if someone set replyTo
> > address then he is trying to invoke that using separate channel .
> Are we starting a new listener in this case??
> Anyway we do not have a control over the replyTo epr given by the
> user... It can be a separate endpoint which is already available...
> AFAIKS in that case even though we useSeparateListener, our client
> side will wait for a response through the listener we setup, which
> would never come that way...
>
> I doubt whether this will solve the issue...
I agree, I don't think this will actually fix the problem described
and adds complexity. Do you know of anyone using the client in this
way?
David
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org