File producer issue while zipping files with apache camel

I am using Zip data format for zipping files. But the issue is i am not able to set dynamic file path even when using CamelFileName header.I can dynamically set the file name but how do i dynamically set the file path also.Here is my code : http://camel.apache.org/schema/spring";> ${bean:utili

Minor Doc issue.

In URL : http://camel.apache.org/swagger-java.html at the bottom it reads: /Examples In the Apache Camel distribution we ship the camel-example-swagger-cdi and *camel-example-swagger-java* which demonstrates using this Swagger component./ I think it should read: /Examples In the Apache Camel

RE: logging/incrementing simple counter

Dear Quinn Yes - what you proposed works, but not if you substitute a property for the file path. Seems like a defect with substituting properties. 1. Following snippet works correctly: Copy file testNaming.xml to file:c:/temp/in Correctly produces file called: C:\temp\in\done\2-fi

Re: camel-s3 Timeout waiting for connection from pool

Hi, I am getting similar exceptions. Did you happen to resolve this issue? If so, how? Thanks -- View this message in context: http://camel.465427.n5.nabble.com/camel-s3-Timeout-waiting-for-connection-from-pool-tp5784483p5792121.html Sent from the Camel - Users mailing list archive at Nabble

Re: Handling errors

To close this discussion, Claus's solution, along with try, catch and process, clauses, worked for me. The route looks like this: from(destinations) .doTry() .to("foo:bar") .doCatch(Exception.class) .process((exchange) -> handleException(exchange)); And the method to add the ex

Re: Handling errors

Ah, nice. I did not see that. Thanks for pointing it out. (And I'll check out that chapter, too.) On Tue, Jan 3, 2017 at 1:15 PM, Claus Ibsen wrote: > Hi > > There is this FAQ > http://camel.apache.org/why-is-the-exception-null-when-i- > use-onexception.html > > On Tue, Jan 3, 2017 at 9:31 PM,

Re: Handling errors

Hi There is this FAQ http://camel.apache.org/why-is-the-exception-null-when-i-use-onexception.html On Tue, Jan 3, 2017 at 9:31 PM, Robert Huffman wrote: > Well, of course I read that, but all I want is access to the actual > Exception objects in my test. I can add the try/catch clauses, but as >

Re: Handling errors

If you don't care about a particular Exception why don't you just have a global error handler that simply routes the exchange to some error handler route. There you can log whatever you want or stop the flow. Here are some ways to access various properties. .setHeader("CamelMessageId", simple("${i

Re: Handling errors

Have you tried getting the exception from the exchange? https://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchange.html#getException() > On Jan 3, 2017, at 1:31

Re: Handling errors

Well, of course I read that, but all I want is access to the actual Exception objects in my test. I can add the try/catch clauses, but as nearly as I can tell the only thing you can do with the catch is route to another endpoint. Isn't there a simple way to get at the underlying exceptions? On Tu

Re: Camel -Mqtt Producer and ProducerTemplate

Anybody have any suggestions on this?? -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Mqtt-Producer-and-ProducerTemplate-tp5792073p5792114.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Handling errors

Hi You should not build your own, but use what is OOTB http://camel.apache.org/error-handling-in-camel.html If you have Camel in Action book then it has a full chapter devoted to error handling. On Tue, Jan 3, 2017 at 7:44 PM, Robert Huffman wrote: > I'm having trouble understanding how to wr

Handling errors

I'm having trouble understanding how to write and use an error handler. The use case is testing a custom Camel component. I would like to have an error handler that just collects any exceptions thrown by the endpoint's producer. I somewhat naively assumed this would be simple. I thought the Camel

Re: Special characters in URL's

@Vitalii, thanks for your help. I was able to overcome using another approach that also suits me. After looking at this carefully I've noticed that the "#" in "to" URL is not that relevant and after all i could just parse part of the url in order to create the route. After this I've made the redi

Re: Springboots vs Osgi // for Camel Apps

I concur. Employing OSGI features like service registry adds significant load according to our tests. Actually we switched from FUSE to Spring Boot during last year. The reason is very simple: in our experience OSGI features were rarely used and classloader hell / testing problems are real. Best r

Re: Special characters in URL's

There are two things to consider: 1) Server never receives anything after #. It's a purely client-side feature to navigate inside the page. It's never sent to server. 2) uri in the logs below is camel endpoint uri, not http one.Path looks correct to me, but please see (1). Best regards, Vitalii Ty

Re: [ANNOUNCE] - Introducing Apache Camel IDEA plugin

Excellent, will try it out shortly! On Tue, Jan 3, 2017 at 1:29 PM, Andrea Cosentino-2 [via Camel] < ml-node+s465427n5792097...@n5.nabble.com> wrote: > Great work! :-) > > Thanks! > -- > Andrea Cosentino > -- > Apache Camel PMC Member > Apache Karaf Committer > Ap

Re: Serializable headers lost by JmsBinding

OK! I'll change it to only camel :) -- View this message in context: http://camel.465427.n5.nabble.com/Serializable-headers-lost-by-JmsBinding-tp5792049p5792100.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Serializable headers lost by JmsBinding

Yes, but you'll need to edit the issue a bit. We only take care of Apache Camel, for Fuse you have to ask to RH support. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd

Re: Serializable headers lost by JmsBinding

So, now that I follow the correct step to report the problem, can you reopen this? https://issues.apache.org/jira/browse/CAMEL-10666 Thank you :) -- View this message in context: http://camel.465427.n5.nabble.com/Serializable-headers-lost-by-JmsBinding-tp5792049p5792098.html Sent from the Ca

Re: [ANNOUNCE] - Introducing Apache Camel IDEA plugin

Great work! :-) Thanks! -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Tuesday, January 3, 2017 1:25 PM, Claus Ibsen wrote: A new plugin for Jet

[ANNOUNCE] - Introducing Apache Camel IDEA plugin

A new plugin for Jetbrains IDEA editor has been created. The plugin adds support for Apache Camel providing completions for Camel endpoints. In other words you can press ctrl + space when editing Camel endpoints and IDEA will present you with a list of possible endpoint options you can use; the sa

Re: Serializable headers lost by JmsBinding

Feel free to raise a JIRA :-) -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Tuesday, January 3, 2017 11:54 AM, davide_cavestro wrote: Andrea Co

Re: Special characters in URL's

Yes, same behavior. As far as I can understand from the logs it seems that the URL is changed when camel is building the routes and any URL that is placed either in to or from is parsed and encoded. -- View this message in context: http://camel.465427.n5.nabble.com/Special-characters-in-URL-s-t

Re: Serializable headers lost by JmsBinding

Andrea Cosentino-2 wrote > This is related to this > > https://issues.apache.org/jira/browse/CAMEL-9584 > ... It seems that CAMEL-9584 partially restored the feature lost with camel 2.16. Would it be worth adding an /allowSerializedHeaders/ ur

Re: Special characters in URL's

Yes, I don't want the URL to be encoded. I'm using jetty. Please find below an example of my routes configuration and startup log. from("jetty:http://0.0.0.0:8080/xpto/#/accounts) .to("http://localhost/xpto/QK7SYGTE2#/screens/170375275/?bridgeEndpoint=true&throwExceptionOnFailure=

camel-cxf drop charset

I use servicemix 7.0.0.m2 (which use camel 2.16.3) to route jax-ws web service call; Call the webservice directly, the http header in response contains Content-Type: text/xml;charset=UTF-8 Call the webservice throw camel-cxf, the http header in response contains Content-Type: text/xml The c

Re: Springboots vs Osgi // for Camel Apps

The packaging as spring boot or OSGi application should not affect the performance. You should be able to scale OSGi packagings in the same way as spring boot by adding more instances. One problem with spring boot is that it is more difficult to package several integrations into one image. OSG