[
https://issues.apache.org/jira/browse/SLING-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794947#comment-13794947
]
Carsten Ziegeler commented on SLING-3171:
-----------------------------------------
[[email protected]] What about definining two constants for such
properties in the Job class? A client starting the job can set them (or not)
> Deprecate job name handling
> ---------------------------
>
> Key: SLING-3171
> URL: https://issues.apache.org/jira/browse/SLING-3171
> Project: Sling
> Issue Type: Task
> Components: Extensions
> Affects Versions: Extensions Event 3.2.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> The job name feature is disturbing, complicated to implement and usually not
> needed: it is used to handle the case where the same job is created more than
> once. This can usually easily be handled by the client code creating the job,
> especially with the new topology stuff.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
