You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Timothee Maret (JIRA)" <ji...@apache.org> on 2017/03/06 08:39:33 UTC

[jira] [Updated] (SLING-6211) Clarify AbstractJcrEventTrigger request addition strategy

     [ https://issues.apache.org/jira/browse/SLING-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothee Maret updated SLING-6211:
----------------------------------
    Fix Version/s:     (was: Content Distribution Core 0.2.6)
                   Content Distribution Core 0.2.8

> 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
>             Fix For: Content Distribution Core 0.2.8
>
>
> 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
(v6.3.15#6346)