Thanks, that certainly helps.  I didn't know about the setProperty method
from the DSL.

FWIW - I think I found another option by making use of:

Exchange.getUnitOfWork().addSynchronization(...)

from a Processor implementation and then I believe I have the full
request/response available in the Synchronization callback.

Dave
--


RomKal wrote:
> 
> 2008/3/7, dtabwhite <[EMAIL PROTECTED]>:
>>  Should there be separate "outflow" processors?  For example, I'd like to
>> be
>>  able to "get at" the full exchange prior to the jetty component writing
>> the
>>  response.  If there is such a thing and I've simply missed it (quite
>>  likely...), please clue me in.
> 
> I'm not sure if you are still interested in the answer, but let me
> give you 'a clue'.
> 
> If you want to have original request AND response just record the
> request somewhere (in a property) like:
> 
> from("jetty:http://localhost:1234/test";)
> .convertBodyTo(String.class)
> .setProperty("originalIn", body())
> .to("http://foo:2345/bar";)
> .process(new MyProcessorUsingOriginalInPropertyToAccessRequest());
> 
> Roman
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-to-get-the-%22whole%22-Http-exchange-%28i.e.-request-response%29-tp15903881s22882p16012629.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to