Re: use gradle to build apache camel application

Hi, I've been working with the Camel and Gradle in the past. If you just plan to create fat jars with Camel inside, the Gradle+Camel works like a charm. Cheers! pt., 3.07.2015 o 15:54 użytkownik Wilson MacGyver napisał: > In my case, I'm building a standalone app. So I was planning to use the

Re: MDC logging does not work with camel.routeId anymore

Yes, it's part of the JBoss Fuse 6.2 stack, so Apache Karaf 2.4 -- View this message in context: http://camel.465427.n5.nabble.com/MDC-logging-does-not-work-with-camel-routeId-anymore-tp5768851p5768855.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: MDC logging does not work with camel.routeId anymore

Hi Another guy had some karaf trouble with this. Have you upgraded Karaf also? And what version do you use? On Fri, Jul 3, 2015 at 3:37 PM, rwijngaa wrote: > Hi, > > We migrated from camel 2.12 to 2.15 and noticed that our MDC logging didn't > work anymore. > When we removed {camel.routeId} from

Re: use gradle to build apache camel application

In my case, I'm building a standalone app. So I was planning to use the application plugin It's encouraging to hear a couple of positive experience. Thanks On Fri, Jul 3, 2015 at 2:24 AM Tim Dudgeon wrote: > The gradle tomcat plugin works fine for running a camel based project. > https://githu

Re: using spock to test camel

Actually I was more thinking of using Spock with https://camel.apache.org/camel-test.html I use intellij so I haven't run into any refactoring issues with groovy On Fri, Jul 3, 2015 at 2:26 AM Tim Dudgeon wrote: > Spock works fine with camel. > After all camel is just java. > The only downside

MDC logging does not work with camel.routeId anymore

Hi, We migrated from camel 2.12 to 2.15 and noticed that our MDC logging didn't work anymore. When we removed {camel.routeId} from the logging definition, all worked again. Any ideas? Regards Rino -- View this message in context: http://camel.465427.n5.nabble.com/MDC-logging-does-not-work-

MDC logging does not work with camel.routeId anymore

Hi, We migrated from camel 2.12 to 2.15 and noticed that the {camel.routeId} in our MDC logger is no longer honored. Worse: it doesn't log anything anymore (we don't see "MDC logger is enabled for context xyz") untill you remove {camel.routeId}, then it logs again. Our mdc log def: Any ideas?

Re: Mocking Endpoints Query

Hi See the advice with section in the testing guide. Also there is a stub endpoint you can use to stub a real component. You can then the stub component to shadow hibernate etc. On Fri, Jul 3, 2015 at 10:26 AM, Coombes Paul (RTH) OUH wrote: > Dear Camel Guru's > I have a query regarding testing

Re: Consuming messages in camel cdi

Hi Tchari, I'm having this same problem with CDI and a POJO consumer with an annotated method @Consumer("direct:someEndpoint"). I get the error message "no consumers available on endpoint". I inspected the CDI registry (this.camelContext.getRegistry()) and I can see my POJO is in the registry.

Re: cxfrs, jaxrs and camel-boot

Hi We have this code in the CXF demo (contributed by a CXF user): https://github.com/apache/cxf/blob/master/distribution/src/main/release/samples/jax_rs/jaxrs_spring_boot/src/main/java/sample/rs/service/SampleRestWSApplication.java I wonder if the problem is no link exists between Spring Dispa

users@camel.apache.org

Hi, I am using the camel 2.13.1. When I tried to use the pop3 endpoint url with the password: *$%^&*()*(&^%$%&*()__)&*^%^&*()_)&*^%* I got the below exception. I took a look at the source code URISupport.parseQuery method it regards the ')&' chars of the password content as the end of the RAW.

RE: Wrong charset when using FTP2 component, locale issue?

Hi Steve, Thanks, I didn't know this actually. Does it seem like a bug for which a ticket should be logged? My ideas to try to solve this: - Change the locale in the Docker image we use - If that doesn't work, implement a custom processor that does the splitting Thanks /Gustav -Original Me

Mocking Endpoints Query

Dear Camel Guru's I have a query regarding testing of a Java DSL route and how to effectively mock endpoints. I have a SpringRouteBuilder (see following) that polls a database table via the hibernate component, with the results being split into individual result items which are transformed into

Re: Invalid content was found starting with element 'exchangeProperty'

Maybe you somehow got mixed Camel versions on the classpath etc. Make sure you have only the same version of Camel. On Fri, Jul 3, 2015 at 9:42 AM, bharadwaj wrote: > i am trying to upgrade jboss fuse 6.1.0 to 6.2.0. > earlier camel 2.12 - > > > myProperty > > > > camel property ex

Re: Invalid content was found starting with element 'exchangeProperty'

i am trying to upgrade jboss fuse 6.1.0 to 6.2.0. earlier camel 2.12 - myProperty camel property expression changed since camel 2.15 onwards : myProperty but when i try to use exchangeProperty in recipientList as above,it's throwing an error. invalid content found

Re: Invalid content was found starting with element 'exchangeProperty'

Can you provide more details. On Fri, Jul 3, 2015 at 9:03 AM, bharadwaj wrote: > Hi, > > Camel 2.15.1 is not able to identify the exchangeProperty in recipientList. > > nested exception is org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: > Invalid content was found starting with element 'ex

Invalid content was found starting with element 'exchangeProperty'

Hi, Camel 2.15.1 is not able to identify the exchangeProperty in recipientList. nested exception is org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'exchangeProperty' -- View this message in context: http://camel.465427.n5.nabble.com/Inv