[
https://issues.apache.org/jira/browse/SLING-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-6211:
-----------------------------------
Fix Version/s: (was: Content Distribution Core 0.3.0)
> Clarify AbstractJcrEventTrigger request addition strategy
> ---------------------------------------------------------
>
> Key: SLING-6211
> URL: https://issues.apache.org/jira/browse/SLING-6211
> Project: Sling
> Issue Type: Task
> Components: Content Distribution
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Priority: Major
>
> We should clarify the logic behind
> [AbstractJcrEventListener#addToList|https://github.com/apache/sling/blob/trunk/contrib/extensions/distribution/core/src/main/java/org/apache/sling/distribution/trigger/impl/AbstractJcrEventTrigger.java#L150]
> as that the addition mechanism seems to rely on the last request added,
> which seems wrong as events may come in in an unsorted manner (not consistent
> with the order the changes they refer to were done).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
