[jira] Commented: (CAMEL-2081) camel-quartz - should not store JobDetail in body but as header

["Sergey Zolotaryov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/CAMEL-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58631#action_58631 ] 

Sergey Zolotaryov commented on CAMEL-2081:
------------------------------------------

In our project we were using exactly the behaviour which was removed by this fix - we were using a converter to create a body from JobDetail object. Since transition to camel 2.2.0 we had to replace a nice solution with an intermediate processor which looks up the jobDetail header and converts it to the right body.  Which is not that nice.

The problem is that DefaultTypeConverter only converts when there is anything to convert.

Could it be possible to have a quartz endpoint property that would force a non-null body with JobDetail object in it?

> camel-quartz - should not store JobDetail in body but as header
> ---------------------------------------------------------------
>
>                 Key: CAMEL-2081
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2081
>             Project: Apache Camel
>          Issue Type: Improvement
>    Affects Versions: 1.6.1, 2.0.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> Currently a quartz object JobDetail is stored in the Camel Message body.
> We should not do this but store it as header instead.
> Then camel-quartz is also the same as the camel timer endpoint that also have a {{null}} body.
> Then it also fixes problems where people have to set an empty body themself, for example as here:
> http://www.nabble.com/sql-throwing-oracle-17004-ORA-17004-error-td25955346.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.