Hi Asankha, When a request comes if you know which scenario, then you can use reference parameters for this transaction, as an alternative to saving a state in your context.
Assuming addressing is engaged, you can send out ref params in the
ReplyTo epr and get them back to you.
- Chinthaka
Asankha C. Perera wrote:
> I was writing some sample Synapse configurations to illustrate the new
> configuration language and came across this requirement...
>
> Scenario 1: The StockQuote client sends a stock quote request to
> synapse, and synapse routes this to the actual service, receives the
> response and sends this back to the client
>
> Scenario 2: A custom stock quote client sends a custom stock quote
> request, which synapse "transforms" into a standard stock quote and
> sends to the actual service. Now once the response is received, the
> client expects this to be "transformed" back again as a custom response
> and returned.
>
> However right now synapse cannot handle case #2 for synchronous
> responses, as it might be required to support both scenarios at the same
> time, and it has no way to differentiate between the responses in the
> two cases.
>
> I was thinking of saving the original To address (of the request) as a
> property into the MessageContext of the response, so that this could be
> used to mediate the response as necessary? We may be able to use the new
> XPath extension function we introduced as follows:
>
> <filter source="synapse:get-property('request/To')"
> regex=".*/StockQuote.*">
> .....
> </filter>
>
> Do you think this is a good idea?
>
> asankha
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
signature.asc
Description: OpenPGP digital signature
