Camel Development

This forum is an archive for the mailing list dev@camel.apache.org (more options) Messages posted here will be sent to this mailing list.

The Nabble Camel forums are now read-only. You need to subscribe to the mailing lists in order to be able to send emails. Requests to grant permissions to post to the forums will be ignored.

1 ... 391392393394395396397 ... 443
Topics (15498)
Replies Last Post Views Sub Forum
[jira] Commented: (CAMEL-1364) Add BindyKeyValuePairFormat to handle content formatted with key value pairs fields like we have in FIX, EMX messages by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Commented: (CAMEL-1364) Add BindyKeyValuePairFormat to handle content formatted with key value pairs fields like we have in FIX, EMX messages by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Created: (CAMEL-1408) File component - better support for absolute path by JIRA jira@apache.org
1
by JIRA jira@apache.org
[jira] Created: (CAMEL-1407) Camel-quartz - improve setting of cron expression to be more cron like by JIRA jira@apache.org
2
by JIRA jira@apache.org
[jira] Created: (CAMEL-1406) DelayProcessor should handle interrupting while shutting down by JIRA jira@apache.org
1
by JIRA jira@apache.org
Re: Problems in implementing Loadbalance using ActiveMQ and Camel by Claus Ibsen-2
0
by Claus Ibsen-2
Re: svn commit: r748757 - /camel/trunk/camel-core/src/main/java/org/apache/camel/component/mock/MockEndpoint.java by Claus Ibsen-2
0
by Claus Ibsen-2
[jira] Created: (CAMEL-1403) Integration tests may stall by JIRA jira@apache.org
2
by JIRA jira@apache.org
[jira] Commented: (CAMEL-1364) Add BindyKeyValuePairFormat to handle content formatted with key value pairs fields like we have in FIX, EMX messages by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Resolved: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Issue Comment Edited: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Issue Comment Edited: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Issue Comment Edited: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Issue Comment Edited: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Issue Comment Edited: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Issue Comment Edited: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes by JIRA jira@apache.org
0
by JIRA jira@apache.org
Re: Data-driven routing by jstrachan
5
by jstrachan
[jira] Resolved: (CAMEL-1366) EndpointMessageListener should respect ExchangePattern by JIRA jira@apache.org
0
by JIRA jira@apache.org
[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 message to by JIRA jira@apache.org
2
by JIRA jira@apache.org
[jira] Issue Comment Edited: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Created: (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 by JIRA jira@apache.org
1
by JIRA jira@apache.org
[jira] Issue Comment Edited: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Commented: (CAMEL-1366) EndpointMessageListener should respect ExchangePattern by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Created: (CAMEL-1384) ExchangeHelper should respect ExchangePattern.InOptionalOut by JIRA jira@apache.org
3
by JIRA jira@apache.org
[jira] Created: (CAMEL-1401) JaxbDataFormat is not thread-safe by JIRA jira@apache.org
2
by JIRA jira@apache.org
[jira] Created: (CAMEL-1400) Restlet default binding does not acknowledge Fault message in the exchange when creating a response by JIRA jira@apache.org
1
by JIRA jira@apache.org
Problems in implementing Loadbalance using ActiveMQ and Camel by pockeylady
0
by pockeylady
Camel - Development (activemq)
[jira] Updated: (CAMEL-1366) EndpointMessageListener should respect ExchangePattern by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Commented: (CAMEL-1366) EndpointMessageListener should respect ExchangePattern by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Issue Comment Edited: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Resolved: (CAMEL-1115) document - logical queue support for ibatis by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Issue Comment Edited: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Issue Comment Edited: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Commented: (CAMEL-1364) Add BindyKeyValuePairFormat to handle content formatted with key value pairs fields like we have in FIX, EMX messages by JIRA jira@apache.org
0
by JIRA jira@apache.org
[jira] Issue Comment Edited: (CAMEL-1373) Use CamelCase for Header keys instead of package name prefixes by JIRA jira@apache.org
0
by JIRA jira@apache.org
1 ... 391392393394395396397 ... 443