You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2011/01/24 12:59:46 UTC
[jira] Closed: (SLING-1823) Use ConfigAdmin configurations for
queues
[ https://issues.apache.org/jira/browse/SLING-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-1823.
-----------------------------------
> 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.