Supun,
When the destination is generated by sender, does the sender block
waiting for the remote broker to generating the destination? If that
is the case we can still move this destination generating logic to the
receiver and make the sender block waiting for receiver until it
generates the destination.
Yes. This is a good workaround. I forgot the fact that it was possible
to get the AMQP message headers to let the server know the ReplyTo
destination name. So, WS-A ReplyTo and AMQP ReplyTo together would do
the trick.
Yes I agree with you about the user setting the replyTo address. That
localhost:6060 should be configured in the axis2.xml to make that
work. That means we are duplicating an information that we already
have. If the user sets a replyTo address like the above, my preference
is what ever set in the axis2.xml for transport receiver should be
overridden by the user input.
Well my concern is if we really want to let the client programmer
manipulate the separate listener in dual-channel case.
Ideally what the client programmer should do is just call *
axis2_options_set_use_separate_listener(options, env, AXIS2_TRUE);*
Don't you think so?
Thanks
Danushka
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
