Re: Camel 2.7.1 graceful termination.

Hi Ashwin, thanks for the quick response. This is indeed a strange behavior. I will try to create a use-case that reproduces the problem and let you know. -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf Committer & PMC Apache ServiceMix

stateful EIP patterns and clustering Camel

Some of the EIP patterns are stateful. For example aggregator collects a group of messages 1-2-3 and sends the aggregated one once all 3 have arrived. When messages 1 and 2 have arrived, state = messages 1 and 2. Another example is resequencer. We are running multiple (now 2) instances of Camel to

extending Camel by implementing your own custom EIP?

Can I extend Camel by implementing my own custom EIP http://camel.apache.org/enterprise-integration-patterns.html? I have a case where all messages A need to be delayed if message B-start has arrived, until message B-end arrives, when all messages A should be sent forward. This may or may not be d

Re: stateful EIP patterns and clustering Camel

There is a JIRA ticket to improved the resequencer to allow a pluggable repository. AFAIK its the last stateful EIP that doesnt offer that. Another stateful EIP is the idempotent consumer. On Thu, May 19, 2011 at 9:44 AM, janne postilista wrote: > Some of the EIP patterns are stateful. For exam

Re: extending Camel by implementing your own custom EIP?

Just implement your own Processor, and use .process in the DSL. If you want to introduce new keywords in the DSL, you need to either - extend RouteBuilder and offer that in Java DSL only. And requre end user to use your custom RouteBuilder - change the source code in camel-core to introduce the EI

Re: Multiple remote connection to the same host but different users

Any update on this? Did you try my suggestion? On Tue, May 3, 2011 at 8:55 AM, Claus Ibsen wrote: > Hi > > Thanks for reporting back. > > Try instead in the camel-http component to patch by doing this: > > Add >    implements ServicePoolAware > to HttpProducer > > And then report back if that fi

Re: stateful EIP patterns and clustering Camel

- Throttler http://camel.apache.org/throttler.html is also kind of a stateful EIP. If an endpoint can handle 10 requests per second, and there are something between 1 and 5 camels running in a clustered setup (depending on which ones are up and which down), how can we specify a throttler that is co

Karaf features file references mvn:org.apache.karaf.assemblies.features/standard/2.2.0/xml/features

Hi, The Camel standard features file contains: mvn:org.apache.karaf.assemblies.features/standard/2.2.0/xml/features Is this beneficial, as it ties the version of Camel in to a specific version of karaf? Without that line the user will be required to specify the karaf url themselves, but that's

Re: Karaf features file references mvn:org.apache.karaf.assemblies.features/standard/2.2.0/xml/features

Hi, As apache-camel feature is using the karaf features, such as Jetty and Spring. These features need a certain version of Karaf, so we specify the repository in the camel feature file. On 5/19/11 7:43 PM, James Talbut wrote: Hi, The Camel standard features file contains: mvn:org.apache.

Re: Karaf features file references mvn:org.apache.karaf.assemblies.features/standard/2.2.0/xml/features

Thanks Willem, Do you really need a specific version? i.e. should camel not work with Karaf 2.2.1? Is it better to force people to use "known good" versions of Karaf, Camel, Spring, etc. or to allow them to upgrade a single component at will? My preference would be for documenting what the known

Re: Karaf features file references mvn:org.apache.karaf.assemblies.features/standard/2.2.0/xml/features

On Thu, May 19, 2011 at 1:56 PM, James Talbut wrote: > Thanks Willem, > > Do you really need a specific version? > i.e. should camel not work with Karaf 2.2.1? > > Is it better to force people to use "known good" versions of Karaf, Camel, > Spring, etc. or to allow them to upgrade a single compon

Re: Karaf features file references mvn:org.apache.karaf.assemblies.features/standard/2.2.0/xml/features

Hi guys, from a general point of view, I prefer to not define Karaf in the feature set. The Karaf features are available by default in the Karaf runtime. So simply adding: war will install the war feature provided by Karaf. Pros: - you aren't link to a Karaf version Cons: - the featu

Re: Karaf features file references mvn:org.apache.karaf.assemblies.features/standard/2.2.0/xml/features

You can do it at the feature level war not at the repositories level. I think it's more elegant to not use Karaf features URL in the and use the version of the feature. Regards JB On 05/19/2011 02:05 PM, Claus Ibsen wrote: On Thu, May 19, 2011 at 1:56 PM, James Talbut wrote: Thanks Will

Re: Needing to push objects out for some reason

I found a partial solution. If I delay starting any components until 10 seconds after starting ActiveMQ, everything is fine. My guess is that it won't route items already on the queue, if it was there before the camel-context file initializes? Is there any control I can use, from a client pov, to

Re: Karaf features file references mvn:org.apache.karaf.assemblies.features/standard/2.2.0/xml/features

+1 for this suggestion. I think we could add a option to let the karaf feature validate plugin to load the features that karaf has before starting the validation. On 5/19/11 8:16 PM, Jean-Baptiste Onofré wrote: Hi guys, from a general point of view, I prefer to not define Karaf in the featur

Re: Karaf features file references mvn:org.apache.karaf.assemblies.features/standard/2.2.0/xml/features

FYI, I submitted a patch for that in CAMEL-3995. Regards JB On 05/19/2011 03:59 PM, Willem Jiang wrote: +1 for this suggestion. I think we could add a option to let the karaf feature validate plugin to load the features that karaf has before starting the validation. On 5/19/11 8:16 PM, Jean-

Re: Problem writing message to file

Hi, Based on a look at your code, you register/add a route only after you pick up your first message. I also do not see code where you send the received message into the route (though I assume you are doing so). Do you have a check in your code to see whether the route is up and running before yo

aws-sqs queue running into exception

Hello all, I am trying to create a queue from aws-sqs with valid credentials.But it is running into exception when I start it . Following is the sample code that I used. JDK 1.6 Camel :2.8-SNAPSHOT JndiRegistry jndi = new JndiRegistry(new JndiContext()); AWSCre

Re: aws-sqs queue running into exception

Hi You have mixed versions of Camel on your classpath. The log say Camel 2.5.0 rg.apache.camel.impl.DefaultCamelContext - Apache Camel 2.5.0 (CamelContext: camel-1) is starting On Thu, May 19, 2011 at 5:48 PM, Sri wrote: > Hello all, > > I am trying to create a queue from aws-sqs with valid c

Re: aws-sqs queue running into exception

Thanks Claus! It works now. -- View this message in context: http://camel.465427.n5.nabble.com/aws-sqs-queue-running-into-exception-tp4410078p4410122.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: lost header (ActiveMQ)

You said that one of the headers is missing, so I assume others made it through fine. If so, try switching from List to a List and see if you have the same issue (might be bumping up against an unsupported type or something). Also, if can you narrow this down to a unit test, post it so we can tak

Re: Problem writing message to file

as Ashwin said, there are a few issues with your approach...notably, you shouldn't define your route in a loop... Also, if you need to poll from a queue every 300ms...then you can use http://camel.apache.org/content-enricher.html poll enrich , like this... from("timer://myTimer?fixedRate=true&pe

expression and spring dsl

Hi all, is there any simple way to specify a custom expression in the spring dsl? i didn't find a simple way to do it. I did an iterator implementing expression and the iterator api is used in a split EIP but not the expression one. the expression api should be used to be fully working. here i

an un-easy way to use camel-xpath in:header() function

Using camel's in:header() xpath function, we can deal with xml stored in message header very easy; for example: in:header('bookstore')/child::book[price<100] The setHeader could retrieve all cheaper books(price less than 100) from a bookstore xml (which already

Simple route with JMS queue is not working

I am trying to compose a route by connecting them via a jms queue. The route does not work. messages emitted by the srcText are not capture in the destination at all ("data.txt"). can you tell if thre is a mistake in this? I use Camel 2.7.1.

Re: an un-easy way to use camel-xpath in:header() function

Have you looked at the Validation component? http://camel.apache.org/validation.html On Fri, May 20, 2011 at 7:10 AM, ext2 wrote: > Using camel's in:header() xpath function, we can deal with xml stored in > message header very easy; for example: > >in:header('bookstore'

Re: an un-easy way to use camel-xpath in:header() function

Also if null or an empty xml is valid in some situations, then a content based router in front of this should do niely. On Fri, May 20, 2011 at 8:18 AM, Taariq Levack wrote: > Have you looked at the Validation component? > http://camel.apache.org/validation.html > > > On Fri, May 20, 2011 at 7:1