camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-9733) enable dynamic job name in component spring-batch
Date Tue, 22 Mar 2016 06:47:25 GMT

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

Claus Ibsen commented on CAMEL-9733:
------------------------------------

Its a two way street. With a header we only have 1 endpoint and 1 producer. With toD you have
more endpoints/producers.

A header can make sense in some case if the producer would be able to support it easily.

> 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)

Mime
View raw message