Re: Camel JMS Logging question

Hi I think you can configure a custom errorHandler on the JMS endpoint / component and there you can log only what you want. See details at https://github.com/apache/camel/blob/master/components/camel-jms/src/main/docs/jms-component.adoc On Tue, Dec 19, 2017 at 6:54 PM, Кристина Солдатко wrote:

Re: Invoke Camel Backlog Tracer

Hi If you just want to have tracing to log files, then using "trace=true" in is not deprecated and you can use that. On Tue, Dec 19, 2017 at 5:09 PM, Joery Vreijsen wrote: > Hi There! > > First of all this is my first time posting in the the mailing list, so > any feedback is appreciated. > >

Re: Question about using Splitter

Hi, Instead of splitting ImageCollection as the body, I think you just need to split List as the body. On Wed, Dec 20, 2017 at 7:50 AM, Charles Berger < charlesb.yesm...@googlemail.com> wrote: > Hi, > > I'm building my first application using Camel and have a question > about how to use a splitt

Camel Spring boot REST xml

Hello, What is the easiest way to unmarshall an XML payload to an object without having to explicitly create or specify the java class? I am POCing a REST service that consumes an XML message from an older system. In the Camel in Action, 2nd Edition book page 93, it says I can easily use XStr

Question about using Splitter

Hi, I'm building my first application using Camel and have a question about how to use a splitter. My route receives a serialized Java class which contains a private ArrayList of a POJO and getter and setter methods for the list. I convert the serialized class into a its Java representation and

Invoke Camel Backlog Tracer

Hi There! First of all this is my first time posting in the the mailing list, so any feedback is appreciated. Im currently experimenting with the Backlog Tracer as we are currently upgrading our application to Camel 2.20.1 and the “old” Tracer is Deprecated. In the documentation (http://camel.a

Invoke Camel Backlog Tracer

Hi There! First of all this is my first time posting in the the mailing list, so any feedback is appreciated. Im currently experimenting with the Backlog Tracer as we are currently upgrading our application to Camel 2.20.1 and the “old” Tracer is Deprecated. In the documentation (http://camel.apa

Camel JMS Logging question

Hi. My service use MQ and receives some data from it. When connection to MQ is broken - I can see in logs following situation: error report is logged as multiple line text like: December 19, 2017 5:32:47 PM UTC[Camel (camel-1) thread #0 - JmsConsumer[ROUTER]] com.ibm.msg.client.jms.internal.JmsPro

Re: aws-s3 client is immutable when created with the builder

Okay. I am building the 2.20.x branch which is using 2.20.2-SNAPSHOT for dependencies. Hopefully, that will work too. Kendall On 12/19/17, 10:30 AM, "Andrea Cosentino" wrote: You need to use the apache snapshot repository, but usually it's not aligned very well.. My suggestion is building

R: Re: aws-s3 client is immutable when created with the builder

You need to use the apache snapshot repository, but usually it's not aligned very well.. My suggestion is building apache camel from code and get the snapshot in your local repo Inviato da Yahoo Mail su Android Il mar, 19 dic, 2017 alle 18:20, Kendall Shaw ha scritto: Thank you. How do I

Re: aws-s3 client is immutable when created with the builder

Thank you. How do I use the snapshot version? I’ve tried specifying the apache snapshot repository but maven can’t resolve camel-spring-boot-dependencies:pom:2.20.1-SNAPSHOT. Kendall From: Andrea Cosentino Reply-To: Andrea Cosentino Date: Tuesday, December 19, 2017 at 1:25 AM To: "users@camel

R: Jetty consumer responds with a 500 error java.io.IOException: Response header too large

What version of camel are you using? Inviato da Yahoo Mail su Android Il mar, 19 dic, 2017 alle 16:45, Laurentiu Trica ha scritto: Hello, I have a problem with the Jetty consumer. I receive a file with an attached file (Multi-Part Form), but if the file is bigger than a few KB, I get the

Jetty consumer responds with a 500 error java.io.IOException: Response header too large

Hello, I have a problem with the Jetty consumer. I receive a file with an attached file (Multi-Part Form), but if the file is bigger than a few KB, I get the bellow Stack trace. If the file is smaller, everything works fine. The strange part is that for a size of 80KB I still receive the file in

Re: aws-s3 client is immutable when created with the builder

Using camel 2.21.0-SNAPSHOT and adding the credentials inside Application.java I don't have any kind of trouble. [INFO] Using org.apache.camel.cdi.Main to initiate a CamelContext[INFO] Starting Camel ...2017-12-19 10:24:00,812 [cdi.Main.main()] INFO  Version                        - WELD-000900: