André,
alu wrote: > > However, I want to call exchange.getResponse().encodeURL(...) to encode a > URL that includes the session ID. So it's not just the session ID that > needs propagating, my endpoint really want access to the session context > through an HttpExchange instance... Is this possible in those subsequent > Processors, or should I try a complete different design direction? > It sounds you want to respond to a form submission from a browser. Camel is no a web server. It's a messaging system. I don't think there is a reason to maintain sessions either with url rewriting or cookies for that matter, but if you really need it, you have full control over the response headers, basically whatever you set as an output header will go into the response (with exceptions you can define). Bela -- View this message in context: http://www.nabble.com/HttpExchange-changes-to-DefaultExchange---expected--tp18809523s22882p18821081.html Sent from the Camel - Users mailing list archive at Nabble.com.
