[
https://issues.apache.org/jira/browse/SLING-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794494#comment-13794494
]
Stefan Seifert commented on SLING-3168:
---------------------------------------
ok, good
why was job priority completely disabled? replaced by the new threadpriority in
QueueConfiguration?
although i've not fully though through the concept of job priorities it looked
useful for me first, if a new job is added to the queues which should run
faster than other jobs - perhaps from the same topic and even running in the
same queue. or was this never implements this way with the old JobPriority enum?
> Deprecating JobUtil class?
> --------------------------
>
> Key: SLING-3168
> URL: https://issues.apache.org/jira/browse/SLING-3168
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> the JobUtil class is deprecated by 90%. perhaps its better to deprecated it
> completely and move the remaining 10% to a new location or other classes more
> suitable. This would solve the inconsistency with the JobUtil.JobPriority
> enum as well, which is not part of the Job interface, whereas JobType is part
> of the Job interface.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
