[
https://issues.apache.org/jira/browse/SLING-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790696#comment-14790696
]
Stefan Egli commented on SLING-4761:
------------------------------------
bq. a) the view changes if just properties change
yes, the view 'object' changes - but not the content of the view, ie the list
of instances is the same
bq. b) as the job handling only acts on change on some properties, it does not
handle all view changes
hm, as I read the
[code|https://github.com/apache/sling/blob/trunk/bundles/extensions/event/src/main/java/org/apache/sling/event/impl/jobs/config/JobManagerConfiguration.java#L567]
it should already also handle the TOPOLOGY_CHANGED case - so I'm assuming it
already handles view changes. so I dont quite see a bug yet in that
handleTopologyEvent.. perhaps a subtle one: when only irrelevant properties
change, then it doesn't stop/start - which will maybe leave the job handler to
eventually stop as it's swallowing the latest (and thus current) event.
bq. c) due to a) and b) the issue needs to be solved in the jobs handling
yes. probably the safest is to [not swallow the
event|https://github.com/apache/sling/blob/trunk/bundles/extensions/event/src/main/java/org/apache/sling/event/impl/jobs/config/JobManagerConfiguration.java#L551]
for irrelevant property changes
> Latest view seems to get marked as not current
> ----------------------------------------------
>
> Key: SLING-4761
> URL: https://issues.apache.org/jira/browse/SLING-4761
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Discovery Impl 1.1.0, Discovery Impl 1.1.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
