[
https://issues.apache.org/jira/browse/SLING-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-1823.
-------------------------------------
Resolution: Fixed
Use configuration admin now for queue configurations; the main queue is a
configuration of the job manager.
To support old style configuration through job properties, a mechanism detects
such config properties, looks for a already configured/running queue and uses
it. If not existing, a new queue with the props from the job is started. This
basically ensures compatibility with the old style.
> Use ConfigAdmin configurations for queues
> -----------------------------------------
>
> Key: SLING-1823
> URL: https://issues.apache.org/jira/browse/SLING-1823
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: Extensions Event 2.4.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.0.0
>
>
> Currently the jobs send to the job handler might contain queue configuration
> information, like a queue name, parallel settings etc. These props are used
> to create queues. This approach has a least two potential problems:
> - What happens if two jobs specify the same queue name with different
> settings?
> - The developer creating the code to send the job might not be the person
> deciding what is processed in which queue and how
> Therefore it would make more sense to have a queue as a configuration in the
> ConfigAdmin . this would make maintenance easier and allows to have a single
> place for queue configurations. Of course the old props should still be
> supported for compatibility.
> The configurations can then be easily added, viewed and monitored through the
> web console.
> The main queue is a configuration which is always available
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
