Re: StreamCaching in Camel 1.6

Hi Claus, yes, it seems to have an effect because the lifecycle-strategy is different when disabling JMX. The Constructor of the DefaultCamelContext uses either DefaultLifecycleStrategy or InstrumentationLifecycleStrategy. This also has influence on the error handling strategy. Jens -- View

Re: StreamCaching in Camel 1.6

Wow nice job! I'll make sure that I try 1.6.1 soon. Thanks a lot Claus. -- View this message in context: http://www.nabble.com/StreamCaching-in-Camel-1.6-tp22305654p22581500.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.

Re: Static buffer field in HTTPConduit

Hi, I posted this via the wrong Nabble Forum. This is of course a CXF issue. Please ignore it. Sorry for my confusion, Jens -- View this message in context: http://www.nabble.com/Re%3A-Static-buffer-field-in-HTTPConduit-tp24809334p24809334.html Sent from the Camel - Users mailing list archive

Type Converters in Camel 2.0

Hi, What is the expected behavior in Camel 2.0 if no type converter is found for a conversion? According to the http://camel.apache.org/type-converter.html documentation starting with Camel 1.5 a NoTypeConversionAvailableException should be thrown. This seems not to be the case in Camel 2.0

IoSession data in Exchange created by MinaConsumer

Hi, in 1.x we had access to the IoSession via the MinaExchange. Although this wasn't the best way to get data from the IoSession, we were able to get things like remote and local address, which are sometimes relevant to routing. In 2.0 the MinaExchange is gone and access to the IoSession isn't

Re: IoSession data in Exchange created by MinaConsumer

// and we should add a nice type converter method so you can do without ugly casting MimaMessage mina = exchange.getIn(MinaMessage.class); I don't think that this is supported by Exchange. There is only a getIn() method that takes no parameters. -- View this message in context:

Re: JMX in Camel 2.1 - Processor MBeans

Hi Claus, I simply changed the last route of the example: route errorHandlerRef=dlc from uri=activemq:queue:stock/ delayconstant100/constant/delay bean ref=stock method=transform/ setHeader headerName=foo

Re: JMX in Camel 2.1 - Processor MBeans

numbers for it (e.g. how often it was called). For such a case I would not necessarily be interested in manipulating it (e.g. starting/stopping). Jens Claus Ibsen-2 wrote: On Thu, Oct 8, 2009 at 9:57 AM, _Jens jens.riemschnei...@icw.de wrote: Just debugged this a bit and it seems that processors

No connection reuse with recipientList and Mina Endpoints

Hi, I have run into an issue with a .recipientList() using Mina endpoints (Camel 2.1). Basically, I was changing a route from using static .to() calls into a more dynamic .recipientList() call. With the .to() calls IoSessions were reused to send data. However, with the .recipientList() it seems

2.3-SNAPSHOT: Stream Caching again enabled by Bug Fix for Camel-2686 and CAMEL-2694 (rev 941275)?

Hi, it seems to me that the DefaultHTTPBinding again uses a CachedOutputStream. This means that the binding cannot be used anymore with longer streams and that the streamCache option on the CamelContext bean is ignored. Is this going to be the way the caching is done in 2.3? Thanks, Jens --

Re: 2.3-SNAPSHOT: Stream Caching again enabled by Bug Fix for Camel-2686 and CAMEL-2694 (rev 941275)?

can still configure the CachedOutputStream by using the camelContext properties, I don't know what kind of issue that the changes introduced to you. Willem _Jens wrote: Hi, it seems to me that the DefaultHTTPBinding again uses a CachedOutputStream. This means that the binding cannot

Re: 2.3-SNAPSHOT: Stream Caching again enabled by Bug Fix for Camel-2686 and CAMEL-2694 (rev 941275)?

don't know why are your going to disable it. Willem _Jens wrote: Hi Willem, thanks for your quick reply. The issue is that I cannot disable streamCaching in 2.3-SNAPSHOT anymore. This is what was changed in DefaultHttpBinding.parseBody: Before: // otherwise use input