[jira] [Commented] (CAMEL-6826) Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing

[ https://issues.apache.org/jira/browse/CAMEL-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623511#comment-14623511 ] James Carman commented on CAMEL-6826: - So you are the sole person who can make this

[jira] [Commented] (CAMEL-6826) Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing

[ https://issues.apache.org/jira/browse/CAMEL-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623512#comment-14623512 ] James Carman commented on CAMEL-6826: - You mean it's fast enough after the changes

[jira] [Reopened] (CAMEL-6826) Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing

[ https://issues.apache.org/jira/browse/CAMEL-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman reopened CAMEL-6826: - Assignee: James Carman Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing

[jira] [Resolved] (CAMEL-6826) Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing

[ https://issues.apache.org/jira/browse/CAMEL-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman resolved CAMEL-6826. - Resolution: Fixed Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing

[jira] [Closed] (CAMEL-6826) Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing

[ https://issues.apache.org/jira/browse/CAMEL-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman closed CAMEL-6826. --- Estimated Complexity: Moderate (was: Unknown) Use Mock Objects Instead of Live HazelcastInstances

[jira] [Commented] (CAMEL-7023) Add hawtio goal to camel plugin

[ https://issues.apache.org/jira/browse/CAMEL-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837989#comment-13837989 ] James Carman commented on CAMEL-7023: - That's James Carman, btw. :) Add hawtio goal

[jira] [Resolved] (CAMEL-6927) Bean Transformer throwing org.apache.camel.TypeConversionException: Error during type conversion from type: due argument type mismatch

[ https://issues.apache.org/jira/browse/CAMEL-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman resolved CAMEL-6927. - Resolution: Not A Problem Looks like the user was unknowingly capitalizing on a bug in the oder

[jira] [Commented] (CAMEL-6927) Bean Transformer throwing org.apache.camel.TypeConversionException: Error during type conversion from type: due argument type mismatch

[ https://issues.apache.org/jira/browse/CAMEL-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13815065#comment-13815065 ] James Carman commented on CAMEL-6927: - Thanks for closing, Sree. I haven't had time

[jira] [Comment Edited] (CAMEL-6927) Bean Transformer throwing org.apache.camel.TypeConversionException: Error during type conversion from type: due argument type mismatch

[ https://issues.apache.org/jira/browse/CAMEL-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812874#comment-13812874 ] James Carman edited comment on CAMEL-6927 at 11/4/13 2:52 PM: --

[jira] [Comment Edited] (CAMEL-6927) Bean Transformer throwing org.apache.camel.TypeConversionException: Error during type conversion from type: due argument type mismatch

[ https://issues.apache.org/jira/browse/CAMEL-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812874#comment-13812874 ] James Carman edited comment on CAMEL-6927 at 11/4/13 2:52 PM: --

[jira] [Commented] (CAMEL-6927) Bean Transformer throwing org.apache.camel.TypeConversionException: Error during type conversion from type: due argument type mismatch

[ https://issues.apache.org/jira/browse/CAMEL-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812874#comment-13812874 ] James Carman commented on CAMEL-6927: - Event is your class, right? Bean Transformer

[jira] [Commented] (CAMEL-6927) Bean Transformer throwing org.apache.camel.TypeConversionException: Error during type conversion from type: due argument type mismatch

[ https://issues.apache.org/jira/browse/CAMEL-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812018#comment-13812018 ] James Carman commented on CAMEL-6927: - Sree, take a look at this example:

[jira] [Commented] (CAMEL-6927) Bean Transformer throwing org.apache.camel.TypeConversionException: Error during type conversion from type: due argument type mismatch

[ https://issues.apache.org/jira/browse/CAMEL-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13811642#comment-13811642 ] James Carman commented on CAMEL-6927: - It looks like the code in question was

[jira] [Commented] (CAMEL-6826) Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing

[ https://issues.apache.org/jira/browse/CAMEL-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13800770#comment-13800770 ] James Carman commented on CAMEL-6826: - This is still in-progress, unless you just want

[jira] [Updated] (CAMEL-6833) Atomic Number Producer Uses Wrong Name

[ https://issues.apache.org/jira/browse/CAMEL-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-6833: Summary: Atomic Number Producer Uses Wrong Name (was: Atomic Number Producer Uses Wrong Cache

[jira] [Work started] (CAMEL-6843) Hazelcast Map Support Uses Wrong Verb Envict

[ https://issues.apache.org/jira/browse/CAMEL-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-6843 started by James Carman. Hazelcast Map Support Uses Wrong Verb Envict -- Key:

[jira] [Resolved] (CAMEL-6843) Hazelcast Map Support Uses Wrong Verb Envict

[ https://issues.apache.org/jira/browse/CAMEL-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman resolved CAMEL-6843. - Resolution: Fixed Now using new constant EVICTED. Hazelcast Map Support Uses Wrong Verb Envict

[jira] [Updated] (CAMEL-4015) camel-hazelcast - Allow to specify operation in uri instead of just as a header

[ https://issues.apache.org/jira/browse/CAMEL-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-4015: Attachment: (was: 0001-CAMEL-4015-camel-hazelcast-uri-format.patch) camel-hazelcast - Allow

[jira] [Updated] (CAMEL-4015) camel-hazelcast - Allow to specify operation in uri instead of just as a header

[ https://issues.apache.org/jira/browse/CAMEL-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-4015: Attachment: (was: CAMEL-4015.patch) camel-hazelcast - Allow to specify operation in uri

[jira] [Updated] (CAMEL-4015) camel-hazelcast - Allow to specify operation in uri instead of just as a header

[ https://issues.apache.org/jira/browse/CAMEL-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-4015: Attachment: (was: CAMEL-4015-2.patch) camel-hazelcast - Allow to specify operation in uri

[jira] [Resolved] (CAMEL-4015) camel-hazelcast - Allow to specify operation in uri instead of just as a header

[ https://issues.apache.org/jira/browse/CAMEL-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman resolved CAMEL-4015. - Resolution: Fixed Romain, please let us know if this addresses your need. Great suggestion! I

[jira] [Commented] (CAMEL-6826) Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing

[ https://issues.apache.org/jira/browse/CAMEL-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13791141#comment-13791141 ] James Carman commented on CAMEL-6826: - Spring tests have been updated as well as the

[jira] [Resolved] (CAMEL-6833) Atomic Number Producer Uses Wrong Cache Name

[ https://issues.apache.org/jira/browse/CAMEL-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman resolved CAMEL-6833. - Resolution: Fixed Atomic Number Producer Uses Wrong Cache Name

[jira] [Work started] (CAMEL-6833) Atomic Number Producer Uses Wrong Cache Name

[ https://issues.apache.org/jira/browse/CAMEL-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-6833 started by James Carman. Atomic Number Producer Uses Wrong Cache Name Key: CAMEL-6833

[jira] [Work started] (CAMEL-6833) Atomic Number Producer Uses Wrong Cache Name

[ https://issues.apache.org/jira/browse/CAMEL-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-6833 started by James Carman. Atomic Number Producer Uses Wrong Cache Name Key: CAMEL-6833

[jira] [Created] (CAMEL-6843) Hazelcast Map Support Uses Wrong Verb Envict

James Carman created CAMEL-6843: --- Summary: Hazelcast Map Support Uses Wrong Verb Envict Key: CAMEL-6843 URL: https://issues.apache.org/jira/browse/CAMEL-6843 Project: Camel Issue Type: Bug

[jira] [Commented] (CAMEL-6826) Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing

[ https://issues.apache.org/jira/browse/CAMEL-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790034#comment-13790034 ] James Carman commented on CAMEL-6826: - I have implemented mocks for the consumer

[jira] [Assigned] (CAMEL-4015) camel-hazelcast - Allow to specify operation in uri instead of just as a header

[ https://issues.apache.org/jira/browse/CAMEL-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman reassigned CAMEL-4015: --- Assignee: James Carman camel-hazelcast - Allow to specify operation in uri instead of just

[jira] [Assigned] (CAMEL-6826) Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing

[ https://issues.apache.org/jira/browse/CAMEL-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman reassigned CAMEL-6826: --- Assignee: James Carman Use Mock Objects Instead of Live HazelcastInstances to Speed Up

[jira] [Created] (CAMEL-6833) Atomic Number Producer Uses Wrong Cache Name

James Carman created CAMEL-6833: --- Summary: Atomic Number Producer Uses Wrong Cache Name Key: CAMEL-6833 URL: https://issues.apache.org/jira/browse/CAMEL-6833 Project: Camel Issue Type: Bug

[jira] [Created] (CAMEL-6826) Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing

James Carman created CAMEL-6826: --- Summary: Use Mock Objects Instead of Live HazelcastInstances to Speed Up Testing Key: CAMEL-6826 URL: https://issues.apache.org/jira/browse/CAMEL-6826 Project: Camel

[jira] [Commented] (CAMEL-6768) @Header @Body @Property bean parameter binding - add mandatory option

[ https://issues.apache.org/jira/browse/CAMEL-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783704#comment-13783704 ] James Carman commented on CAMEL-6768: - I don't mean we would have two different

[jira] [Commented] (CAMEL-6768) @Header @Body @Property bean parameter binding - add mandatory option

[ https://issues.apache.org/jira/browse/CAMEL-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783703#comment-13783703 ] James Carman commented on CAMEL-6768: - I don't mean we would have two different

[jira] [Issue Comment Deleted] (CAMEL-6768) @Header @Body @Property bean parameter binding - add mandatory option

[ https://issues.apache.org/jira/browse/CAMEL-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-6768: Comment: was deleted (was: I don't mean we would have two different attributes on each annotation.

[jira] [Updated] (CAMEL-4015) camel-hazelcast - Allow to specify operation in uri instead of just as a header

[ https://issues.apache.org/jira/browse/CAMEL-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-4015: Attachment: 0001-CAMEL-4015-camel-hazelcast-uri-format.patch Claus, try this patch instead.

[jira] [Commented] (CAMEL-6768) @Header @Body @Property bean parameter binding - add mandatory option

[ https://issues.apache.org/jira/browse/CAMEL-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783380#comment-13783380 ] James Carman commented on CAMEL-6768: - We should probably change the attribute name,

[jira] [Commented] (CAMEL-6783) getFeatures() method of CxfEndpoint only accept AbstractFeature but Feature

[ https://issues.apache.org/jira/browse/CAMEL-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13781935#comment-13781935 ] James Carman commented on CAMEL-6783: - It's okay to take List? extends Feature? on the

[jira] [Comment Edited] (CAMEL-6783) getFeatures() method of CxfEndpoint only accept AbstractFeature but Feature

[ https://issues.apache.org/jira/browse/CAMEL-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13781935#comment-13781935 ] James Carman edited comment on CAMEL-6783 at 9/30/13 3:34 PM: --

[jira] [Updated] (CAMEL-4015) camel hazelcast uri format

[ https://issues.apache.org/jira/browse/CAMEL-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-4015: Attachment: CAMEL-4015-2.patch Sure, Claus. Can you just apply this patch file over top of the

[jira] [Commented] (CAMEL-6783) getFeatures() method of CxfEndpoint only accept AbstractFeature but Feature

[ https://issues.apache.org/jira/browse/CAMEL-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13781348#comment-13781348 ] James Carman commented on CAMEL-6783: - That would make things worse, because then the

[jira] [Commented] (CAMEL-4015) camel hazelcast uri format

[ https://issues.apache.org/jira/browse/CAMEL-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13781349#comment-13781349 ] James Carman commented on CAMEL-4015: - Sorry about the first patch. Forgot that we're

[jira] [Commented] (CAMEL-4015) camel hazelcast uri format

[ https://issues.apache.org/jira/browse/CAMEL-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780815#comment-13780815 ] James Carman commented on CAMEL-4015: - I'm implementing this now.

[jira] [Updated] (CAMEL-4015) camel hazelcast uri format

[ https://issues.apache.org/jira/browse/CAMEL-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-4015: Attachment: CAMEL-4015.patch This patch implements the feature as I understand the request.

[jira] [Commented] (CAMEL-6768) @Header @Body @Property bean parameter binding - add mandatory option

[ https://issues.apache.org/jira/browse/CAMEL-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780866#comment-13780866 ] James Carman commented on CAMEL-6768: - We don't want to change the existing behavior,

[jira] [Commented] (CAMEL-6670) Throttler EIP - Add JMX attribute to know if hit limit currently (eg its throttling state)

[ https://issues.apache.org/jira/browse/CAMEL-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780877#comment-13780877 ] James Carman commented on CAMEL-6670: - I have an idea how to fix this, but I don't

[jira] [Updated] (CAMEL-6792) Camel Test Support needs a new Method

[ https://issues.apache.org/jira/browse/CAMEL-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-6792: Attachment: CAMEL-6792.patch I believe this takes care of it. Camel Test Support

[jira] [Commented] (CAMEL-6783) getFeatures() method of CxfEndpoint only accept AbstractFeature but Feature

[ https://issues.apache.org/jira/browse/CAMEL-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780887#comment-13780887 ] James Carman commented on CAMEL-6783: - This change could cause a regression. Are we

[jira] [Updated] (CAMEL-6783) getFeatures() method of CxfEndpoint only accept AbstractFeature but Feature

[ https://issues.apache.org/jira/browse/CAMEL-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-6783: Attachment: CAMEL-6783.patch In case we decide to accept the regression risk of this change, I'm

[jira] [Commented] (CAMEL-4015) camel hazelcast uri format

[ https://issues.apache.org/jira/browse/CAMEL-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780890#comment-13780890 ] James Carman commented on CAMEL-4015: - Romain, it actually allows you to either use

[jira] [Updated] (CAMEL-6771) ConcurrentModificationException thrown from inside camel splitter

[ https://issues.apache.org/jira/browse/CAMEL-6771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-6771: Attachment: CAMEL-6771.patch This should fix the problem. I was having trouble creating a unit

[jira] [Created] (CAMEL-6748) Optimize File Producers by Skipping Header Evaluation

James Carman created CAMEL-6748: --- Summary: Optimize File Producers by Skipping Header Evaluation Key: CAMEL-6748 URL: https://issues.apache.org/jira/browse/CAMEL-6748 Project: Camel Issue

[jira] [Updated] (CAMEL-6734) Introduce CamelFileNameConsumed Header

[ https://issues.apache.org/jira/browse/CAMEL-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-6734: Summary: Introduce CamelFileNameConsumed Header (was: Introduce CamelConsumedFileName Header)

[jira] [Updated] (CAMEL-6734) Introduce CamelFileNameConsumed Header

[ https://issues.apache.org/jira/browse/CAMEL-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-6734: Description: On the producing side, we have CamelFileNameProduced. It would be nice if we had

[jira] [Updated] (CAMEL-6748) Optimize File Producers by Skipping Header Evaluation

[ https://issues.apache.org/jira/browse/CAMEL-6748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-6748: Attachment: CAMEL-6748.patch This patch implements the improvement and includes a WARN-level

[jira] [Commented] (CAMEL-6734) Introduce CamelConsumedFileName Header

[ https://issues.apache.org/jira/browse/CAMEL-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13765324#comment-13765324 ] James Carman commented on CAMEL-6734: - Thanks for the tip, Claus. I was having an

[jira] [Updated] (CAMEL-6734) Introduce CamelConsumedFileName Header

[ https://issues.apache.org/jira/browse/CAMEL-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-6734: Attachment: CAMEL-6734.patch Here's a patch implementing the improvement.

[jira] [Commented] (CAMEL-5668) camel-jetty - A soap fault should trigger http response code 500

[ https://issues.apache.org/jira/browse/CAMEL-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13467024#comment-13467024 ] James Carman commented on CAMEL-5668: - Sorry about introducing the test failure. I

[jira] [Commented] (CAMEL-5668) camel-jetty - A soap fault should trigger http response code 500

[ https://issues.apache.org/jira/browse/CAMEL-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13466609#comment-13466609 ] James Carman commented on CAMEL-5668: - I believe this is reported against the wrong

[jira] [Updated] (CAMEL-5668) camel-jetty - A soap fault should trigger http response code 500

[ https://issues.apache.org/jira/browse/CAMEL-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-5668: Attachment: CAMEL-5668.patch Here's a patch that implements what I think you're looking for. I

[jira] [Updated] (CAMEL-5668) camel-jetty - A soap fault should trigger http response code 500

[ https://issues.apache.org/jira/browse/CAMEL-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-5668: Attachment: CAMEL-5668.patch Here's another patch that patches both the http and http4 components.

[jira] [Updated] (CAMEL-5668) camel-jetty - A soap fault should trigger http response code 500

[ https://issues.apache.org/jira/browse/CAMEL-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-5668: Attachment: (was: CAMEL-5668.patch) camel-jetty - A soap fault should trigger http

[jira] [Commented] (CAMEL-5668) camel-jetty - A soap fault should trigger http response code 500

[ https://issues.apache.org/jira/browse/CAMEL-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13466616#comment-13466616 ] James Carman commented on CAMEL-5668: - We should really think about consolidating this

[jira] [Commented] (CAMEL-5557) Camel-ZeroMQ Component

[ https://issues.apache.org/jira/browse/CAMEL-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13462763#comment-13462763 ] James Carman commented on CAMEL-5557: - What's wrong with just leaving this in extras

[jira] [Created] (CAMEL-5641) JmsBinding Does Not Handle BigInteger and BigDecimal Properly

James Carman created CAMEL-5641: --- Summary: JmsBinding Does Not Handle BigInteger and BigDecimal Properly Key: CAMEL-5641 URL: https://issues.apache.org/jira/browse/CAMEL-5641 Project: Camel

[jira] [Updated] (CAMEL-5641) JmsBinding Does Not Handle BigInteger and BigDecimal Properly

[ https://issues.apache.org/jira/browse/CAMEL-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-5641: Attachment: CAMEL-5641.patch Fix with test case. JmsBinding Does Not Handle

[jira] [Commented] (CAMEL-5464) camel-jms consumer doesn't send back a reply in all cases

[ https://issues.apache.org/jira/browse/CAMEL-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13445928#comment-13445928 ] James Carman commented on CAMEL-5464: - Okay, cool! Sorry about the regression. I was

[jira] [Comment Edited] (CAMEL-5464) camel-jms consumer doesn't send back a reply in all cases

[ https://issues.apache.org/jira/browse/CAMEL-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13445928#comment-13445928 ] James Carman edited comment on CAMEL-5464 at 9/1/12 3:30 AM: -

[jira] [Commented] (CAMEL-4725) Add support for Callable statements

[ https://issues.apache.org/jira/browse/CAMEL-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442885#comment-13442885 ] James Carman commented on CAMEL-4725: - You could also switch to H2. I have used that

[jira] [Updated] (CAMEL-5464) camel-jms consumer doesn't send back a reply in all cases

[ https://issues.apache.org/jira/browse/CAMEL-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated CAMEL-5464: Attachment: CAMEL-5464.patch Here's a patch that implements option #2. Let me know if you see any

[jira] [Commented] (CAMEL-5293) Sending map that contains a serialized object that is not a primitive type causes an exception to be thrown.

[ https://issues.apache.org/jira/browse/CAMEL-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13280668#comment-13280668 ] James Carman commented on CAMEL-5293: - You can try setting transferExchange=true on