Re: Lately (2.14) NullPointerExceptions instead of TypeConversionExceptions

Probably the stacktrace will not help: the npe is thrown on the line where i use the object returned from getBody(Some.class); The problem ist that no exception is thrown by getBody(Some.class) but null is returned. So there must be a path that returns null. -- View this message in context:

Re: jmx- annotated RouteBuilder not showing up in JConsole

Thanks for the hint that helped much - i tried both. on first site there is no different in extending ServiceSupport (onStart, onStop mus be added) or implementing Service (start, stop methods must be added). -- View this message in context:

Re: Date format issue in xstream marshalling.

Hello, Can any one please help in retaining the date value instead converting to GMT? Thanks, Sayed -- View this message in context: http://camel.465427.n5.nabble.com/Date-format-issue-in-xstream-marshalling-tp5758860p5760697.html Sent from the Camel - Users mailing list archive at

Re: EventNotifierSupport - Endpoint ID accessible ?

There is already stats per processor (eg each step in the route) - these stats are in the jmx. On Mon, Dec 15, 2014 at 11:46 AM, Michael Täschner m.taesch...@gmail.com wrote: Hi, yes these are not Endpoints in the routes but I saw no clear definitions for the steps and each can be given an id

Programmatically referring to route/context names within routes,

Hi, I have a generic dead letter queue handler. Before messages are put onto the dead letter queue, my routes log details of the exceptions (via an interceptor within the same context). I'd like to also stamp the messages with the route and context from which the exception was thrown. I could

Re: Programmatically referring to route/context names within routes,

Hi See the simple language which has many details. And the message history eip http://camel.apache.org/message-history On Mon, Dec 15, 2014 at 12:29 PM, Jeremy Gooch jer...@huwun.com wrote: Hi, I have a generic dead letter queue handler. Before messages are put onto the dead letter queue,

Re: Changes in Java 8 generics breaking Camel

I am using Camel 2.14.0. I do see one problem, though maybe it's just a lack of understanding of the process you're using to compare results. Annotations like @Consume have a retention policy of runtime, meaning the compiler leaves them in the compiled class file (I believe). Your decompiled

Re: cfx web service client error

Hi Willem now am getting below error Response-Code: 500 Encoding: UTF-8 Content-Type: application/soap+xml; charset=utf-8 Headers: {Cache-Control=[private], connection=[keep-alive], Content-Length=[508], content-type=[application/soap+xml; charset=utf-8], Date=[Mon, 15 Dec 2014 12:14:53 GMT],

Re: Changes in Java 8 generics breaking Camel

Current Camel 2.14.0 is built with JDK7 and we run the CI with JDK8 and didn’t find the issue that you said. Can you create a JIRA and submit a test case for it? -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com

Re: cfx web service client error

It looks like you didn’t setup your camel route rightly? Can you show me your camel route? -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On December 15, 2014 at

Re: Changes in Java 8 generics breaking Camel

Am 15.12.14 14:38 schrieb andrewcelerity unter and...@celerityglobal.com: I am using Camel 2.14.0. I do see one problem, though maybe it's just a lack of understanding of the process you're using to compare results. Annotations like @Consume have a retention policy of runtime, meaning the

Re: Throttling based on content in camel

Hi, Looking at the documentation says that ThrottlingInflightRoutePolicy does throttling that is approximate based, meaning that its more coarse grained and not explicit precise as the Throttler (did a poc and coul. Also it looks like the RoutePolicy applies to the entire Route when compared to

Re: FW: Spring Camel Parent Context

Looks like a JIRA had already been created. Claus wasn't a big fan of the change. https://issues.apache.org/jira/browse/CAMEL-5858 I might try to create a patch and see if there will still be resistance. I can't imagine I'm the only one with a use case of centralized CamelContext

How to avoid cxfrs:rserver adding extra header params (accept-encoding) -

Hi we are using camel cxfrs server to expose our proxy services, The service is exposer is working fine but if the response is more that certain limit looks like the client is not able to receive getting timed out exception. Then we have identified that the camel service adding some extra

Problem with InOnly exchange pattern using with RestDSL

Hello! I'm using spark-java as rest-dsl provider (but I already tried with the servlet component and still didn't work) and I'm having some issues using in only in a rest dsl route: That's the rest configuration: restConfiguration().component(spark-rest).bindingMode(RestBindingMode.json)

Re: cfx web service client error

Hi I have pasted below my java class public class CamelCfxTest extends RouteBuilder { String endPoint = cxf: http://123.231.66.11/gslwsairavailabilitydisplay/Service1.asmx?wsdlURL=galieo.wsdl; // + dataFormat=PAYLOAD // + serviceName={http://tempuri.org/}Service1;

Re: REST DSL Exception Handling

This is when the Json request comes in to the webservice. I am deliberately sending in a malformed Json object, just so that I can handle it - our service will be called by various applications, and I want to be able to send a response back to the caller with the message that the Json is

Re: Problem with InOnly exchange pattern using with RestDSL

Hi Maybe you should use the wire tap eip On Tue, Dec 16, 2014 at 1:17 AM, gabfssilva gabfssi...@gmail.com wrote: Hello! I'm using spark-java as rest-dsl provider (but I already tried with the servlet component and still didn't work) and I'm having some issues using in only in a rest dsl

Re: REST DSL Exception Handling

Hi Thanks for trying. I logged a ticket to support this in next release https://issues.apache.org/jira/browse/CAMEL-8155 On Mon, Dec 15, 2014 at 8:01 PM, restful camel bin...@gmail.com wrote: This is when the Json request comes in to the webservice. I am deliberately sending in a malformed

Re: How to avoid cxfrs:rserver adding extra header params (accept-encoding) -

Adding more informations. I am using Camel 2.14.0 version and we are exposing services using cxfrs component, When the response size is but the response by default the header parameter is set as Transfer-Encoding = chunk, but we are expecting Transfer-Encoding = Identity; in the response header.

Intermittent error: No content to map due to end-of-input

hi guys, I am quite new to Camel. We are using Camel 2.14. I got this intermittent error which is quite annoying. It happens very rarely and randomly. If I send the same request again, it will process just fine. 2014-12-15 17:24:56.700 ERROR 1852673485@qtp-1010937526-2