Build failed in Hudson: Camel #1117

See https://hudson.apache.org/hudson/job/Camel/1117/changes Changes: [hadrian] Consolidate use of assertFileExists [davsclaus] Fixed tests on slow servers. [davsclaus] Fixed test. [davsclaus] CAMEL-3559: Fixed completeFromBatchConsumer on the aggregator. [davsclaus] Added spring XML

[jira] Commented: (CAMEL-3286) camel-jms - Setting TaskExecutor should support both Spring 2.5 and 3.0

[ https://issues.apache.org/jira/browse/CAMEL-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12983638#action_12983638 ] Claus Ibsen commented on CAMEL-3286: trunk: 1060739. I spotted another case where it

[jira] Created: (CAMEL-3560) Detect uncaught exceptions in UoWProcessor to ensure UoW is done even for those uncaught exceptions

Detect uncaught exceptions in UoWProcessor to ensure UoW is done even for those uncaught exceptions --- Key: CAMEL-3560 URL:

[jira] Created: (CAMEL-3561) camel archetypes generate warnings in mvn 3.0.2

camel archetypes generate warnings in mvn 3.0.2 --- Key: CAMEL-3561 URL: https://issues.apache.org/jira/browse/CAMEL-3561 Project: Camel Issue Type: Improvement Components: tooling

[jira] Resolved: (CAMEL-3560) Detect uncaught exceptions in UoWProcessor to ensure UoW is done even for those uncaught exceptions

[ https://issues.apache.org/jira/browse/CAMEL-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3560. Resolution: Fixed trunk: 1060768. Detect uncaught exceptions in UoWProcessor to ensure UoW is

[jira] Resolved: (CAMEL-3542) camel-jms - Request/Reply - ReplyManager should use the concurrentConsumers options

[ https://issues.apache.org/jira/browse/CAMEL-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3542. Resolution: Won't Fix Fix Version/s: (was: 2.7.0) 2.6.0 See section

[jira] Commented: (CAMEL-3171) Allow property placeholders to be used anywhere in Spring XML (and blueprint as well)

[ https://issues.apache.org/jira/browse/CAMEL-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12983672#action_12983672 ] Claus Ibsen commented on CAMEL-3171: See irc chat on this date

[jira] Commented: (CAMEL-3171) Allow property placeholders to be used anywhere in Spring XML (and blueprint as well)

[ https://issues.apache.org/jira/browse/CAMEL-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12983693#action_12983693 ] Claus Ibsen commented on CAMEL-3171: I cannot find out how to define a a custom type

[jira] Commented: (CAMEL-3171) Allow property placeholders to be used anywhere in Spring XML (and blueprint as well)

[ https://issues.apache.org/jira/browse/CAMEL-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12983694#action_12983694 ] Claus Ibsen commented on CAMEL-3171: We can define types at package level so eg we can

[jira] Updated: (CAMEL-3554) The camel transport for cxf should map header fields like the cxfbean component

[ https://issues.apache.org/jira/browse/CAMEL-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated CAMEL-3554: --- Fix Version/s: (was: 2.7.0) 2.6.0 The camel transport for

[jira] Resolved: (CAMEL-3554) The camel transport for cxf should map header fields like the cxfbean component

[ https://issues.apache.org/jira/browse/CAMEL-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved CAMEL-3554. Resolution: Fixed The camel transport for cxf should map header fields like the

[jira] Assigned: (CAMEL-3562) BindyFixedLengthDataFormat does a trim on Fixed Length record

[ https://issues.apache.org/jira/browse/CAMEL-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Karpe reassigned CAMEL-3562: --- Assignee: Ashwin Karpe BindyFixedLengthDataFormat does a trim on Fixed Length record

[jira] Updated: (CAMEL-3562) BindyFixedLengthDataFormat does a trim on Fixed Length record

[ https://issues.apache.org/jira/browse/CAMEL-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Karpe updated CAMEL-3562: Component/s: camel-bindy BindyFixedLengthDataFormat does a trim on Fixed Length record

[jira] Work started: (CAMEL-3562) BindyFixedLengthDataFormat does a trim on Fixed Length record

[ https://issues.apache.org/jira/browse/CAMEL-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-3562 started by Ashwin Karpe. BindyFixedLengthDataFormat does a trim on Fixed Length record -

CAMEL-913 implementation question

I implemented CAMEL-913 in the timer component by adding a Producer and an additional parameter to the endpoint. Time for a sanity check before I submit the patch. New parameter: sendTo - The endpoint to send the incoming Exchange to when the timer fires. Both value may be set in the URI

[jira] Commented: (CAMEL-913) sending a message to a timer or quartz endpoint should create a new timer - which when it fires, a message is sent to an endpoint specified by a header.

[ https://issues.apache.org/jira/browse/CAMEL-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984023#action_12984023 ] Hadrian Zbarcea commented on CAMEL-913: --- I don't really understand the use case. My

Re: CAMEL-913 implementation question

See my comment [1] added to the issue [2]. I cannot see a credible usecase where this feature would be helpful which is not already covered by other camel features. @James, care to explain more? Hadrian [1]

[jira] Updated: (CAMEL-3561) camel archetypes generate warnings in mvn 3.0.2

[ https://issues.apache.org/jira/browse/CAMEL-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-3561: --- Priority: Minor (was: Major) Fix Version/s: (was: 2.6.0) 2.7.0

[jira] Commented: (CAMEL-913) sending a message to a timer or quartz endpoint should create a new timer - which when it fires, a message is sent to an endpoint specified by a header.

[ https://issues.apache.org/jira/browse/CAMEL-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984034#action_12984034 ] Claus Ibsen commented on CAMEL-913: --- Tracy and I had a chat on IRC. I think he

[jira] Issue Comment Edited: (CAMEL-913) sending a message to a timer or quartz endpoint should create a new timer - which when it fires, a message is sent to an endpoint specified by a header.

[ https://issues.apache.org/jira/browse/CAMEL-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984034#action_12984034 ] Claus Ibsen edited comment on CAMEL-913 at 1/20/11 1:11 AM:

[jira] Commented: (CAMEL-913) sending a message to a timer or quartz endpoint should create a new timer - which when it fires, a message is sent to an endpoint specified by a header.

[ https://issues.apache.org/jira/browse/CAMEL-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984035#action_12984035 ] Claus Ibsen commented on CAMEL-913: --- If we use quarz then it has the ability to persist

[jira] Commented: (CAMEL-2989) provider an API to query available endpoints on a component

[ https://issues.apache.org/jira/browse/CAMEL-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984036#action_12984036 ] Claus Ibsen commented on CAMEL-2989: Ben the idea is much more complicated :) James

[jira] Issue Comment Edited: (CAMEL-2989) provider an API to query available endpoints on a component

[ https://issues.apache.org/jira/browse/CAMEL-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984036#action_12984036 ] Claus Ibsen edited comment on CAMEL-2989 at 1/20/11 1:18 AM: -

[DISCUSS] - JMSReplyTo to yourself

Hi Suppose you have a Camel route from(activemq:queue:foo) .process(xxx) And a client sends a message to the foo queue with a JMSReplyTo header set with the queue:foo destination. The client has essentially told to send a reply back to the same queue as the message was consumed. Currently

Re: [DISCUSS] - JMSReplyTo to yourself

Hi Claus, most of the time, we have a REQUEST queue and a RESPONSE queue. I've never seen a response post on the same queue. By default, it makes sense to log a WARN when posting on the same queue. The use of disableReplyTo is too restrictive because the users could use a replyTo to another

[jira] Commented: (CAMEL-2989) provider an API to query available endpoints on a component

[ https://issues.apache.org/jira/browse/CAMEL-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984046#action_12984046 ] Christian Schneider commented on CAMEL-2989: I basically like the idea but we

Re: [DISCUSS] - JMSReplyTo to yourself

Hi Claus, I also have not seen people using the same queue for replies. Although it would be possible o do so using message selectors. So if we want to block this we should allow people to override. Something like ?allowReplyToSameDestination=true Christian Am 20.01.2011 07:38, schrieb

Hudson build is back to normal : Camel #1118

See https://hudson.apache.org/hudson/job/Camel/1118/changes

Re: [DISCUSS] - JMSReplyTo to yourself

Yes, CXF JMS transport support to use same queue for request and response, and it use the selector to check the correlationID. I think the failed test is caused by the message exchange pattern is InOut, and if the test box is slower to shutdown the camel context, you will get as many as