You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "cziegeler (via GitHub)" <gi...@apache.org> on 2023/03/13 09:15:15 UTC

[GitHub] [sling-org-apache-sling-jcr-base] cziegeler commented on pull request #9: [SLING-11741] Provide alternative terminology for inequitable terms

cziegeler commented on PR #9:
URL: https://github.com/apache/sling-org-apache-sling-jcr-base/pull/9#issuecomment-1465772342

   I think there is a change of a timing issue here as well - old configuration gets delivered to using component, configuration listener kicks in and updates the configuration, the component is updated with the new configuration. For this we should minimize the cascading effects - in practice that means we need to check whether handling of "modified" events is in place.  But I suggest to look at this once we have applied a first version of this PR.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@sling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org