[jira] Resolved: (CAMEL-1380) Aggregator - completedPredicate should be renamed to completionPredicate to be in line with wording

[ https://issues.apache.org/activemq/browse/CAMEL-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1380. Resolution: Fixed Aggregator - completedPredicate should be renamed to completionPredicate to

[jira] Commented: (CAMEL-1364) Add BindyKeyValuePairFormat to handle content formatted with key value pairs fields like we have in FIX, EMX messages

[ https://issues.apache.org/activemq/browse/CAMEL-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49968#action_49968 ] Charles Moulliard commented on CAMEL-1364: -- @Willem, The directory that you mention

[jira] Commented: (CAMEL-1364) Add BindyKeyValuePairFormat to handle content formatted with key value pairs fields like we have in FIX, EMX messages

[ https://issues.apache.org/activemq/browse/CAMEL-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49969#action_49969 ] Willem Jiang commented on CAMEL-1364: - @Charles Can you create a patch for

[jira] Commented: (CAMEL-1364) Add BindyKeyValuePairFormat to handle content formatted with key value pairs fields like we have in FIX, EMX messages

[ https://issues.apache.org/activemq/browse/CAMEL-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49970#action_49970 ] Charles Moulliard commented on CAMEL-1364: -- @Willem, Do I have to update my svn

[jira] Updated: (CAMEL-1364) Add BindyKeyValuePairFormat to handle content formatted with key value pairs fields like we have in FIX, EMX messages

[ https://issues.apache.org/activemq/browse/CAMEL-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Moulliard updated CAMEL-1364: - Attachment: camel-bindy-fixsimple.txt @Hi, Here is the patch for the folder

[jira] Created: (CAMEL-1381) PredicateClause in the fluent builder for building predicates using fluent builder syntax

PredicateClause in the fluent builder for building predicates using fluent builder syntax - Key: CAMEL-1381 URL: https://issues.apache.org/activemq/browse/CAMEL-1381

Re: Problem with jetty endpoint

Hi, I able to run the jetty endpoint with file endpoint successfully and also received expected output (2 file endpoint). Thanks, Ganesh Claus Ibsen-2 wrote: Hi What is the exception you get? To be able to store it as a file it much use something that is InputStream convertable.

Re: Where exception handling should set a handled exception?

Hi Roman Could you add a route example to that. AFAIR this is *only* with the try .. handle DSLs ? I can enlighten that on the DeadLetterChannel we store previoysly occured exception as a property when we do redelivery. There is a constant KEY for it on the Exchange (Camel 2.0) String

[jira] Commented: (CAMEL-1364) Add BindyKeyValuePairFormat to handle content formatted with key value pairs fields like we have in FIX, EMX messages

[ https://issues.apache.org/activemq/browse/CAMEL-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49980#action_49980 ] Willem Jiang commented on CAMEL-1364: - @ Charles I think you still don't put all the

Re: Discussion of scope for next Apache Camel 1.x release

+1 I created a 2.0-M1 version in jira. Let's assign the issues we want to close down in the M1 release and I will cut the release. On Feb 24, 2009, at 8:08 AM, James Strachan wrote: Agreed - lets get 2.0 out ASAP - while releasing bug fixes in 1.6.1. Not sure if we'll ever need a 1.7?

Re: Camel 2.0 - Keys for header problem

Hi I am working on this now, to change it to CamelCase. I am adding xxxConstants classes to the component where we can put the constants for the key names. This allows end users to easy spot which keys we have. I decided for xxxConstants over Constants when end users work with multiple

[jira] Updated: (CAMEL-1364) Add BindyKeyValuePairFormat to handle content formatted with key value pairs fields like we have in FIX, EMX messages

[ https://issues.apache.org/activemq/browse/CAMEL-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Moulliard updated CAMEL-1364: - Attachment: (was: camel-bindy-keyvaluepair.patch) Add BindyKeyValuePairFormat

[jira] Updated: (CAMEL-1364) Add BindyKeyValuePairFormat to handle content formatted with key value pairs fields like we have in FIX, EMX messages

[ https://issues.apache.org/activemq/browse/CAMEL-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Moulliard updated CAMEL-1364: - Attachment: camel-bindy.txt @Willem, Here is a new one. I hope it will be complete.

[jira] Updated: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes

[ https://issues.apache.org/activemq/browse/CAMEL-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-1373: --- Fix Version/s: (was: 2.0.0) 2.0-M1 Use CamelCase for Header keys instead

[jira] Issue Comment Edited: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes

[ https://issues.apache.org/activemq/browse/CAMEL-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49979#action_49979 ] davsclaus edited comment on CAMEL-1373 at 2/25/09 7:04 AM: -

[jira] Assigned: (CAMEL-1004) make it easy to start/stop routes by their definition (RouteBuilder or Route class)

[ https://issues.apache.org/activemq/browse/CAMEL-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan reassigned CAMEL-1004: - Assignee: James Strachan make it easy to start/stop routes by their definition

[jira] Created: (CAMEL-1383) provide a text search - or a way to search by some expression for messages on an endpoint

provide a text search - or a way to search by some expression for messages on an endpoint - Key: CAMEL-1383 URL: https://issues.apache.org/activemq/browse/CAMEL-1383

[jira] Commented: (CAMEL-1383) provide a text search - or a way to search by some expression for messages on an endpoint

[ https://issues.apache.org/activemq/browse/CAMEL-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49988#action_49988 ] James Strachan commented on CAMEL-1383: --- we could support a RAM only lucene based

[jira] Commented: (CAMEL-1364) Add BindyKeyValuePairFormat to handle content formatted with key value pairs fields like we have in FIX, EMX messages

[ https://issues.apache.org/activemq/browse/CAMEL-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49990#action_49990 ] Willem Jiang commented on CAMEL-1364: - @ Charles Did you just changed the dateformat's

[jira] Work started: (CAMEL-1004) make it easy to start/stop routes by their definition (RouteBuilder or Route class)

[ https://issues.apache.org/activemq/browse/CAMEL-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-1004 started by James Strachan. make it easy to start/stop routes by their definition (RouteBuilder or Route class)

[jira] Commented: (CAMEL-1366) EndpointMessageListener should respect ExchangePattern

[ https://issues.apache.org/activemq/browse/CAMEL-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49993#action_49993 ] Michael Chen commented on CAMEL-1366: - exchange.isOutCapable() is always true downstream

[jira] Created: (CAMEL-1384) ExchangeHelper should respect ExchangePattern.InOptionalOut

ExchangeHelper should respect ExchangePattern.InOptionalOut Key: CAMEL-1384 URL: https://issues.apache.org/activemq/browse/CAMEL-1384 Project: Apache Camel Issue Type: Bug

[jira] Resolved: (CAMEL-1377) create a war maven archetype which lets folks spin up a new project which comes with the camel-web application and REST API - but lets folks include whatever dependencies

[ https://issues.apache.org/activemq/browse/CAMEL-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Anstey resolved CAMEL-1377. Resolution: Fixed create a war maven archetype which lets folks spin up a new project

starting, stopping, creating editing routes at runtime now works - CAMEL-1004

Here's a test case to show the kind of thing we can now do... http://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/impl/StartAndStopRoutesTest.java there's now a start/stop route method on CamelContext where you can start or stop individual routes using the route

[jira] Resolved: (CAMEL-1004) make it easy to start/stop routes by their definition (RouteBuilder or Route class)

[ https://issues.apache.org/activemq/browse/CAMEL-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-1004. --- Resolution: Fixed Fix Version/s: (was: 2.1.0) 2.0.0 see

Data-driven routing

After working through Camel-Spring-ActiveMQ configuration and a DSL approach I am still struggling with the pieces necessary to achieve dynamic, data-driven routing for JMS as follows. Each source (ActiveMQ topic or queue) may have 0-n routes, each defined below: 1. Optional xpath expression

Re: Data-driven routing

2009/2/25 jbower1950 jim.bo...@gmail.com: After working through Camel-Spring-ActiveMQ configuration and a DSL approach I am still struggling with the pieces necessary to achieve dynamic, data-driven routing for JMS as follows. Each source (ActiveMQ topic or queue) may have 0-n routes, each

Re: Data-driven routing

I have tried that approach. It was pretty intuitive and made sense. The problem came when I had two routes from the same source (e.g., a log), one portion of which I wanted to route to one topic, the other part going to another topic. It appeared that, using the DSL with two routes, one message