Re: issue with property in REST DSL in blueprint context - Camel 2.19.1

Yes, quite the upgrade... but everything else seems to be working fine so far. ;) I raised a ticket: https://issues.apache.org/jira/browse/CAMEL-11636 Thx! On 04.08.17 13:39, Claus Ibsen wrote: Hi Yeah a change from 2.16.x to 2.19.x is a little bit big upgrade. However this sounds like a lit

Stream closed exception when using camel as http proxy with tomcat servlet

Hello, following the example provided in http://camel.apache.org/how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html, we are using a route definition as follows to proxy an http endpoint via a servlet running in Tomcat 8.5.16: from("servlet:///?matchOnUriPrefix=true") .to("http4://

Camel - The name and slogans ...

Hi, I just read http://camel.apache.org/why-the-name-camel.html I like the slogans and then this groaner popped into my head: "Everything tastes sweeter when it Camel-ized." (as in caramelized: https://en.wikipedia.org/wiki/Caramelization) Let me know if you feel this email is spam and I will

Re: Full example of configuring endpoints in pure Java (without uri strings)

Hello Claus, Thanks a lot for your helpful response. Currently I just set the CamelContext on the endpoints right after I create them and that seems to take care of the wiring between endpoint and component. Regarding the code example I included in my previous email to this list, I had to make a

Re: Issue with camel-elasticsearch5 component

Here is the JIRA in SM https://issues.apache.org/jira/browse/SM-3454 -- Andrea Cosentino  -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Friday, August 4, 2017, 1:46:

Re: Issue with camel-elasticsearch5 component

Try turning on dynamic import on those ES bundles via dev:import-dynamic karaf command. For the issue with the SMX bundle you can log that in the ServiceMix JIRA ticket or in CAMEL. Then Andreas from the Camel/SMX team can take a look, and get those packages to be imported|exported. On Wed, Aug

Re: apache camel toD does not accept a property value of about 40 characters

There is no limit to the length of options in Camel etc, so I would be surprised if there is a bug in Camel in this regard. I suggest to dive deeper. And also test this on newer versions of Camel etc if you can reproduce on a supported branch. 2.17.x is EOL. On Wed, Aug 2, 2017 at 4:21 PM, jephrey

Re: Full example of configuring endpoints in pure Java (without uri strings)

Hi Yeah you can run Camel standalone with that main class or do it by yourself. One comment is that when you create the CxfEndpoint then you need to set the CxfComponent on this instance as well. Ideally you create the endpoints via the uri syntax, or via the component. For some camel component

Re: issue with property in REST DSL in blueprint context - Camel 2.19.1

Hi Yeah a change from 2.16.x to 2.19.x is a little bit big upgrade. However this sounds like a little bug. You are welcome to log a JIRA and we can look at getting this fixed for upcoming releases. On Fri, Aug 4, 2017 at 11:24 AM, claud...@gmail.com wrote: > Hi, > > I'm trying to update from Ca

issue with property in REST DSL in blueprint context - Camel 2.19.1

Hi, I'm trying to update from Camel 2.16.3 to 2.19.1 and experience issues using properties in the REST DSL in blueprint context. I have the following config: path="patient/{patient_id}/events?cutoff_timestamp={cutoff_timestamp}&limit={limit}" produces="application/json" consumes="ap