[jira] [Comment Edited] (CAMEL-9733) enable dynamic job name in component spring-batch

["Tomas Rohovsky (JIRA)" <ji...@apache.org>]

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

Tomas Rohovsky edited comment on CAMEL-9733 at 3/21/16 10:42 PM:
-----------------------------------------------------------------

Hi Jose,

IMO with introduction of a [dynamic to|http://camel.apache.org/message-endpoint.html#MessageEndpoint-DynamicTo] {{toD}} in Camel 2.16, the component specific headers for overriding URI's "host" part (like in camel-sql) lost their meaning. The advantage of {{toD}} is that caching of produces for reuse is provided OOTB.


was (Author: trohovsky):
Hi Jose,

IMO with introduction of a dynamic to {{toD}} in Camel 2.16, the component specific headers for overriding URI's "host" part (like in camel-sql) lost their meaning. The advantage of {{toD}} is that caching of produces for reuse is provided OOTB.

> enable dynamic job name in component spring-batch
> -------------------------------------------------
>
>                 Key: CAMEL-9733
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9733
>             Project: Camel
>          Issue Type: Wish
>          Components: camel-spring-batch
>    Affects Versions: 2.16.2, 2.17.0
>         Environment: any
>            Reporter: Jose Luis Pedrosa
>            Priority: Minor
>             Fix For: 2.17.1
>
>   Original Estimate: 16m
>  Remaining Estimate: 16m
>
> Hi
> Currently springBatch accepts a parameter jobName in the url, which is evaluated during the creation of the endpoint.
> This makes impossible to launch different jobs dinamically.The requested feature would be to make it message context based, in the headers with a parameter 
> "jobNameHeader", which would be evaluated per message. In a similar way as SQL and the columns value parameters.
> If the project is interested and willing to incorporate it into the sources, I could offer me to code it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)