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 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. Supun. On Fri, Nov 14, 2008 at 9:54 AM, Danushka Menikkumbura <[EMAIL PROTECTED]>wrote: > > Is it possible for your receiver to generate the destination and then >> sender to pick the destination from there? >> > Since the transport works with a remote broker, this is not a viable > option. Because it is not guaranteed that the listener is done with creating > the destination by the time the sender is ready to send. > >> Setting the reply to address by client is acceptable. But as you've >> pointed out if this is not set by the client this should be set >> automatically. >> > Well my gut feeling is that letting the user set something like > http://localhost:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__is > not that neat. > >> I think although there is a method to retrieve the replyTo address from >> the receiver, it is not being used internally by axis2/c. >> > True. > > > Danushka > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Software Engineer, WSO2 Inc http://wso2.org Web Services with Axis2/C http://wsaxc.blospot.com
