[
https://issues.apache.org/jira/browse/SLING-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660352#action_12660352
]
Carsten Ziegeler commented on SLING-799:
----------------------------------------
Not 100% sure (I've to check the code), but I think the job handler does not
rely on the order of the nodes in the repository.
The job handler holds the queues in memory in the correct order. In case of a
restart the query fetches the nodes in the correct order by using a sorting on
a property.
However, an ordered folder shouldn't hurt.
> Job Folder is not ordered and results in unordered queue
> --------------------------------------------------------
>
> Key: SLING-799
> URL: https://issues.apache.org/jira/browse/SLING-799
> Project: Sling
> Issue Type: Bug
> Components: Event
> Affects Versions: Extensions Event 2.0.2
> Reporter: Tobias Bocanegra
>
> check code of
> AbstractRepositoryEventHandler.ensureRepositoryPath()
> /**
> * Check if the repository path already exists. If not, create it.
> */
> protected Node ensureRepositoryPath()
> throws RepositoryException {
> final Node node = JcrResourceUtil.createPath(this.repositoryPath,
> EventHelper.NODETYPE_FOLDER,
> EventHelper.NODETYPE_FOLDER,
> this.writerSession, true);
> return node;
> }
> this should use a "sling:OrderedFolder"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
