You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/29 19:08:21 UTC
[jira] [Commented] (CAMEL-10057) Support Spring modular batch
config
[ https://issues.apache.org/jira/browse/CAMEL-10057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399869#comment-15399869 ]
ASF GitHub Bot commented on CAMEL-10057:
----------------------------------------
GitHub user asegarra opened a pull request:
https://github.com/apache/camel/pull/1094
CAMEL-10057: add optional JobRegistry
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/asegarra/camel CAMEL-10057
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1094.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1094
----
commit 697ff58ced3f38f75119e0fa60314087df5818c9
Author: asegarra <an...@outlook.com>
Date: 2016-07-29T18:27:26Z
CAMEL-10057: add optional JobRegistry
----
> Support Spring modular batch config
> ------------------------------------
>
> Key: CAMEL-10057
> URL: https://issues.apache.org/jira/browse/CAMEL-10057
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-batch
> Affects Versions: 2.17.1
> Reporter: Angel Segarra
>
> Currently the spring-batch:jobName component cannot find the jobName in the registry if the project is configured with modular=true in Spring Batch. In a modular batch project the jobs are created in a child context and reference to the Job is typically located using the configured JobRegistry. I suggest an option for injecting a JobRegistry that if set is used to locate Jobs instead of directly in the camel registry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)