Re: svn commit: r748757 - /camel/trunk/camel-core/src/main/java/org/apache/camel/component/mock/MockEndpoint.java

On Sat, Feb 28, 2009 at 1:07 AM, wrote: > Author: hadrian > Date: Sat Feb 28 00:07:13 2009 > New Revision: 748757 > > URL: http://svn.apache.org/viewvc?rev=748757&view=rev > Log: > Fix assertion to pass when a non-String value matches an expected String > value. > > Modified: >     > camel/trunk

[jira] Resolved: (CAMEL-1403) Integration tests may stall

[ https://issues.apache.org/activemq/browse/CAMEL-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1403. Resolution: Fixed Fix Version/s: 2.0.0 Found the problem in a unit test. Fixed it by add

[jira] Assigned: (CAMEL-1403) Integration tests may stall

[ https://issues.apache.org/activemq/browse/CAMEL-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-1403: -- Assignee: Claus Ibsen > Integration tests may stall > --- > >

[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-tabpanel&focusedCommentId=50096#action_50096 ] Hadrian Zbarcea commented on CAMEL-1364: @Charles Do you mind updating the documentat

[jira] Resolved: (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 resolved CAMEL-1373. Resolution: Fixed Yes its done all components have changed keys to CamelCase syntax > Use Came

[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-tabpanel&focusedCommentId=49979#action_49979 ] davsclaus edited comment on CAMEL-1373 at 2/27/09 8:53 AM: - camel

[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-tabpanel&focusedCommentId=49979#action_49979 ] davsclaus edited comment on CAMEL-1373 at 2/27/09 8:27 AM: - camel

[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-tabpanel&focusedCommentId=49979#action_49979 ] davsclaus edited comment on CAMEL-1373 at 2/27/09 8:22 AM: - camel

[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-tabpanel&focusedCommentId=49979#action_49979 ] davsclaus edited comment on CAMEL-1373 at 2/27/09 8:11 AM: - camel

[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-tabpanel&focusedCommentId=49979#action_49979 ] davsclaus edited comment on CAMEL-1373 at 2/27/09 7:50 AM: - camel

[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-tabpanel&focusedCommentId=49979#action_49979 ] davsclaus edited comment on CAMEL-1373 at 2/27/09 7:19 AM: - camel

Re: Data-driven routing

2009/2/27 jbower1950 : > > Thanks to both James and Claus, > > There seem to be several "dynamic" route queries scattered throughout the > web. Both James' example and the new method in 2.0 should be helpful. I am > guessing that I am not alone in trying to solve this problem. Perhaps an > example

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

[ https://issues.apache.org/activemq/browse/CAMEL-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1366. Resolution: Fixed The reply destination is set as a property on the exchange: {code} Destinatio

Re: Data-driven routing

Thanks to both James and Claus, There seem to be several "dynamic" route queries scattered throughout the web. Both James' example and the new method in 2.0 should be helpful. I am guessing that I am not alone in trying to solve this problem. Perhaps an example in the docs? Yesterday I got a pro

[jira] Resolved: (CAMEL-1405) be able to create a jms endpoint easily from a JMS Destination object - as well as to be able to use a property on an Exchange to denote the real JMS destination to send

[ https://issues.apache.org/activemq/browse/CAMEL-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1405. Resolution: Fixed Assignee: James Strachan > be able to create a jms endpoint easily from

[jira] Commented: (CAMEL-1405) be able to create a jms endpoint easily from a JMS Destination object - as well as to be able to use a property on an Exchange to denote the real JMS destination to send

[ https://issues.apache.org/activemq/browse/CAMEL-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50079#action_50079 ] Claus Ibsen commented on CAMEL-1405: There is a JMSConstants for the property. > be able

[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-tabpanel&focusedCommentId=49979#action_49979 ] davsclaus edited comment on CAMEL-1373 at 2/27/09 4:32 AM: - camel

[jira] Assigned: (CAMEL-1385) allow the (transitive) maven dependencies on a module to be displayed in the runtime when we fail to load a component/language/converter

[ https://issues.apache.org/activemq/browse/CAMEL-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-1385: --- Assignee: Willem Jiang > allow the (transitive) maven dependencies on a module to be disp

[jira] Created: (CAMEL-1405) be able to create a jms endpoint easily from a JMS Destination object - as well as to be able to use a property on an Exchange to denote the real JMS destination to send a

be able to create a jms endpoint easily from a JMS Destination object - as well as to be able to use a property on an Exchange to denote the real JMS destination to send a message to --

[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-tabpanel&focusedCommentId=49979#action_49979 ] davsclaus edited comment on CAMEL-1373 at 2/27/09 4:13 AM: - camel

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

[ https://issues.apache.org/activemq/browse/CAMEL-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50068#action_50068 ] Claus Ibsen commented on CAMEL-1366: trunk: Committed revision 748476. > EndpointMessage

Re: Data-driven routing

Hi BTW: We might consider whit Camel 2.0 to add a sample for a real dynamic router where you can create the route in java code and start it for those that are using such thing. This sample uses the dynamic recipient list that is not totally the same: http://camel.apache.org/dynamic-router.html

Re: Data-driven routing

2009/2/26 jbower1950 : > > 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

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

[ https://issues.apache.org/activemq/browse/CAMEL-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1384. Resolution: Fixed Committed revision 748469. > ExchangeHelper should respect ExchangePattern.I

[jira] Created: (CAMEL-1404) Add SPI interface for pluggable Resolvers

Add SPI interface for pluggable Resolvers - Key: CAMEL-1404 URL: https://issues.apache.org/activemq/browse/CAMEL-1404 Project: Apache Camel Issue Type: New Feature Components: camel-core

[jira] Resolved: (CAMEL-1401) JaxbDataFormat is not thread-safe

[ https://issues.apache.org/activemq/browse/CAMEL-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1401. Resolution: Fixed Trunk: Committed revision 748436. 1.x: Committed revision 748450. > JaxbData

[jira] Created: (CAMEL-1403) Integration tests may stall

Integration tests may stall --- Key: CAMEL-1403 URL: https://issues.apache.org/activemq/browse/CAMEL-1403 Project: Apache Camel Issue Type: Bug Components: tests Reporter: Gert Vanthienen Cfr.