: 17:30 Mittwoch, 13.März 2013
Betreff: Re: Premature servlet response
On Wed, Mar 13, 2013 at 1:42 PM, Christian Schäfer wrote:
> Hi,
>
> I removed the on completion as suggested but the problem persists.
> Maybe a similar problem related to the aggregate and their completionHandler
to do your own aggregation.
> regards
> Christian
>
>
>
> Von: Willem jiang
> An: users@camel.apache.org; Christian Schäfer
> Gesendet: 3:27 Dienstag, 12.März 2013
> Betreff: Re: Premature servlet response
>
> Hi,
>
> Have yo
, 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
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
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
