You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/04/20 11:32:58 UTC

[jira] [Commented] (SLING-4638) isCurrent() not always correctly set

    [ https://issues.apache.org/jira/browse/SLING-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502568#comment-14502568 ] 

Carsten Ziegeler commented on SLING-4638:
-----------------------------------------

I assume this also includes that the view object passed to the topology event listeners is updated correctly and can be used within implementations to find out whether the view is still current or not

> isCurrent() not always correctly set
> ------------------------------------
>
>                 Key: SLING-4638
>                 URL: https://issues.apache.org/jira/browse/SLING-4638
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Discovery Impl 1.1.0
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>            Priority: Critical
>             Fix For: Discovery Impl 1.1.2
>
>
> With extending the TOPOLOGY_CHANGING phase in SLING-3432 and follow-up tickets such as SLING-4634 and SLING-4635, the correctness of TopologyView.isCurrent() is very important: currently it is not always correctly set. This must be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)