Re: RestConfiguration with multiple ports

Hi Do you want to have different rest services for different ports? Or do some of the rest services share the ports? Either way its not currently baked in too well in the rest-dsl to allow to pick which rest configuration to user per service. The design was to keep it simple, 1 rest component for

Re: Thrown error ignored in processor

You can stop the route from your component, though mind stopping a route from a route isn't super easy http://camel.apache.org/how-can-i-stop-a-route-from-a-route.html Or you can maybe better add a custom route policy to this route, that detects the exception and validates whether its fatal or not

Exchange has SOAPMessage want to Send to JMS Topic

I am new to the Camel world and what I am trying to do is as follows. 1. There is a route which is Servlet Component which is called by external System. 2. MyServlet CamelComponent Reads the incoming exchange and creates the SOAPMessage. 3. In Next Step I want to send the SOAP message to JMS To

Re: A silly idea?

Thanks for all of your comments, and I've read them carefully. Yes, I agree Karaf is an awesome framework to use hot deployment, and Spring is nice too, and even all the things that I've written on my first thread were extra functionalities, camel don't need to support. The first reason why I've lo

RestConfiguration with multiple ports

I know that via netty4-http I'm able to create multiple HTTP listeners on multiple ports. from("netty4-http:http://localhost:8088";).to(...) from("netty4-http:http://localhost:8087";).to(...) but when using rest configuration it seems I'm limited to the one listener restConfiguration().compone

Re: A silly idea?

I have been using Camel at work for sometimes and I love Camel. Here, we think about Camel having 2 pieces: *component* (I use this term loosely to mean non-route) which is written only in code and *route* which could be written in any particular DSL (groovy, java, xml,...). The component is fixe

Re: A silly idea?

The problem is that people have different requirements for the runtime. For example the hot deployment is a reason to choose OSGi but not everyone needs that. You should have a look at Apache Karaf. It might provide just the environment you search for. I got a tutorial that shows how to deploy yo

Re: Thrown error ignored in processor

Claus, Thanks for the prompt reply. My test case was that my endpoint couldn't get a connection to the server via the api so this error should be fatal (at least to this route) since I can't process any of the files. My problem is how do I signal this to Camel from the code in my component? Rgds,

Re: Thrown error ignored in processor

Hi This is intended. What do you want to happen when the exception is thrown? Should the file component stop totally ? move the file somewhere else / or somerhing else. You can configure much in the Camel error handler. And on the file component to move files that fails to an error directory etc.

Thrown error ignored in processor

Hi, I'm writing my first component. It's reading files and sending them to a NoSql database. The problem is that I can't get it to raise an error if something goes wrong. All that happens is the processor completes and tries again after a short delay. I tried try-catch, and I can log the error, bu

Re: camel-http-common 2.16.1 includes Servlet API 3.0

Aren't same versions of different camel artifacts supposed to be used together? Why is camel-jetty 2.16.1 using 3.1 but it's ok for camel-http4 2.16.1 to be using 3.0? Is that not incompatible within the same versions? If it was not the intention to move to 3.1 but stay in 3.0 for Camel 2.16, then

Re: Bundle is waiting for namespace handlers blueprint

Hello Bruno There's https://issues.apache.org/jira/browse/ARIES-1350 fixed in aries.blueprint.core-1.4.4. Please use this version. regards Grzegorz Grzybek 2016-01-14 14:07 GMT+01:00 Marco Westermann : > Hi, > > can you confirm that the broker bundle stays in grace period? Then that is > an old

Re: Bundle is waiting for namespace handlers blueprint

Hi, can you confirm that the broker bundle stays in grace period? Then that is an old issue. It has something to do with the order the bundles get startet. And that has to do with the server performance.. I had servers where I faced that issue at every start. On some servers I have that issue

Bundle is waiting for namespace handlers blueprint

I'm create an new simple project, just for test, with the blueprint code founded on: - http://camel.apache.org/using-osgi-blueprint-with-camel.html When deploy it over a new uncompresed folder of servicemix (5.5.1) and the log say: INFO | x-5.5.1/deploy | BlueprintContainerImpl | 19 - o

Re: A silly idea?

Hi Kay, Those extra functionalities are outside the scope of the Camel. This is usually where higher level runtime frameworks/servers like Spring Boot, Karaf, etc. kicks in. So just choose the right runtime for your purposes (I personally prefer Spring Boot) and use Camel integration module dedic

Re: Issue with maximumPoolSize & Netty4-http component

Hi Charles, I just created a JIRA[1] for it and will back port the patch CAMEL-8031 to camel-netty4 shortly. [1]https://issues.apache.org/jira/browse/CAMEL-9514  -- Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁

Re: camel-sjms support for JMS 2 in OSGI

Generated a pull request -> https://github.com/apache/camel/pull/768 -- View this message in context: http://camel.465427.n5.nabble.com/camel-sjms-support-for-JMS-2-in-OSGI-tp5776164p5776223.html Sent from the Camel - Users mailing list archive at Nabble.com.