[
https://issues.apache.org/jira/browse/CAMEL-10057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Angel Segarra updated CAMEL-10057:
----------------------------------
Description: 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. (was: 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 for the component
to by default locate a jobRegistry bean to use in case the jobName cannot be
found directly in the camel registry, and alternately to allow configuring the
jobRegistry to use as an option in the URI.)
> 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)
