Hi, I removed the on completion as suggested but the problem persists. Maybe a similar problem related to the aggregate and their completionHandlers?
regards Christian ________________________________ Von: Willem jiang <willem.ji...@gmail.com> An: users@camel.apache.org; Christian Schäfer <syrious3...@yahoo.de> Gesendet: 3:27 Dienstag, 12.März 2013 Betreff: Re: Premature servlet response Hi, Have you went through the onCompletion[1] page? If you want to processor2 take effect, you need to remove the onCompletion from your route. [1]http://camel.apache.org/oncompletion.html -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Monday, March 11, 2013 at 9:44 PM, Christian Schäfer wrote: > Hello, > > currently I have the problem of not beeing able to set servlet response which > was generated by the last processor of my route: > > > servlet-consumer -> processor1 -> onCompletion -> aggregate -> processor2 > (response builder) > > > When I fire my test to the deployed servlet endpoint (camel 2.10.4 @ JBoss > 7.1) it behaves in the order that: > 1. body of processor1 is returned as http response > 2. after that, processor2 starts which is too late as the response is still > sent. > > How to force the route to send the response only when processor2 is done? > > regards > Christian
