[jira] [Assigned] (CAMEL-3354) Allow bean component to return null which will be accepted as a new Message with an empty body

[ https://issues.apache.org/jira/browse/CAMEL-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-3354: -- Assignee: Claus Ibsen Allow bean component to return null which will be accepted as a new

[jira] [Resolved] (CAMEL-3354) Allow bean component to return null which will be accepted as a new Message with an empty body

[ https://issues.apache.org/jira/browse/CAMEL-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3354. Resolution: Duplicate Fix Version/s: (was: 3.0.0) 2.9.0 This is a

[jira] [Resolved] (CAMEL-4384) camel-jms - Request/Reply - Allow null messages to be send back as replies when using ObjectMessage type

[ https://issues.apache.org/jira/browse/CAMEL-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4384. Resolution: Cannot Reproduce Works fine already. I have added unit tests as well. camel-jms -

Re: [DISCUSS] - Apache Camel 2.8.1 release

I also think a 2.8.1 release would be great. Like discussed in another part of this thread as this is a bugfix release upgrades of libs should generally also be only bug fix releases. Christian Am 25.08.2011 09:58, schrieb Claus Ibsen: Hi Its been 1 month since Camel 2.8.0 was released.

[jira] [Resolved] (CAMEL-4375) FilterCreateCamelContextPerClassTest is wrong configured

[ https://issues.apache.org/jira/browse/CAMEL-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-4375. - Resolution: Fixed FilterCreateCamelContextPerClassTest is wrong configured

[jira] [Updated] (CAMEL-4380) FactoryFinder should support to find the class with a right version of class

[ https://issues.apache.org/jira/browse/CAMEL-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-4380: Summary: FactoryFinder should support to find the class with a right version of class (was:

[jira] [Assigned] (CAMEL-4356) faster way of testing for file existence

[ https://issues.apache.org/jira/browse/CAMEL-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-4356: --- Assignee: Willem Jiang faster way of testing for file existence

[jira] [Commented] (CAMEL-4356) faster way of testing for file existence

[ https://issues.apache.org/jira/browse/CAMEL-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13091762#comment-13091762 ] Claus Ibsen commented on CAMEL-4356: Some FTP server may not allow listing using a

[jira] [Resolved] (CAMEL-4367) Camel-netty option encoder and decoder does not work

[ https://issues.apache.org/jira/browse/CAMEL-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-4367. - Resolution: Fixed Fix Version/s: 2.9.0 2.8.1 Applied patch into trunk

Re: svn commit: r1161953 - in /camel/trunk/camel-core/src: main/java/org/apache/camel/component/ main/java/org/apache/camel/component/bean/ main/java/org/apache/camel/component/browse/ main/java/org/a

It should be possible for people to create an endpoint without any component. A component is not mandatory for an endpoint. And the code in the setEndpointUriIfXXX (cant remember the name) where you just try to get a component name from the given uri is not a good idea. The setter should not

[jira] [Created] (CAMEL-4385) DefaultExchange.copy always creates a DefaultMessage even if the source exchange had a custom Message type

DefaultExchange.copy always creates a DefaultMessage even if the source exchange had a custom Message type -- Key: CAMEL-4385 URL: