One way to get around this might be to provide the option of targeting (physical or logical) in the URL of call into Synapse. That way, you don't HAVE to have wsa-to elements.
In the case of the logical mapping in the URL of call itself, additional configuration such as the one Soumadeep is talking about could be used to map to the physical service. Mukund Balasubramanian -----Original Message----- From: Soumadeep Sen Sent: Saturday, February 04, 2006 1:21 PM To: Synapse Subject: [axis2]Concerns about WSATo Header element Paul/Sanjiva, I am a little apprehensive about the way currently we mandate that the wsa-To element in the SOAP header be set by the user/client for Synapse to work. Do you think it would be better to introduce the concept of a contract where the wsa-to element value would be mapped to the actual provider service url in some xml file in Synapse, what the user would put in the wsa-to is more of a proxy url to the actual service. The reason I am putting this across is because why would a user go through Synapse when he can directly send a request to the actual service provider. Let me know if I am missing something here. Best regards Soumadeep --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
