On 26/06/07, Thilina Gunarathne <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
