Re: JMapper Framework

Hi I added a ticket to look into integrating JMapper with Camel out of the box. https://issues.apache.org/jira/browse/CAMEL-5879 On Tue, Dec 11, 2012 at 4:39 PM, Claus Ibsen wrote: > Hi Alessandro > > Thanks for sharing this with us. > > I assume you use some byte code manipulation to have the p

[HEADS UP] - Jetty component and http clients

Hi I have looked at: https://issues.apache.org/jira/browse/CAMEL-5867 The problem is that when using camel-jetty a jetty http client would always be created, even if people only use the jetty consumer. This leads to the jetty http client setup a thread pool with 8 live threads, running for no goo

Re: svn commit: r1420455 - /camel/trunk/camel-core/src/main/java/org/apache/camel/processor/WrapProcessor.java

On Wed, Dec 12, 2012 at 10:03 PM, Christian Müller wrote: > Ok, I reverted the change. > What's your suggested solution? > > The current behavior is not a good solution... > Well for Camel 3.0 we have on the roadmap to refactor the message history eip, which essentially is also the tracer, as it