[
https://issues.apache.org/jira/browse/SLING-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502689#comment-14502689
]
Stefan Egli commented on SLING-4638:
------------------------------------
More fixes in http://svn.apache.org/r1674809 :
* in activate() when delayInitEventUntilVoted is not configured and we're in
isolated mode: set current==false
* in bindTopologyEventListener: when a listener is registered late (==after
activate) then you can already be CHANGING again - which would require
current==false too
* in getTopology(): check if returned topology is isolated OR we're between
CHANGING and CHANGED (for this, mark delayedEventPending as volatile)
* in forcedShutdown(): mark view as old too
> 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)
