[
https://issues.apache.org/jira/browse/SLING-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890051#comment-15890051
]
Konrad Windszus edited comment on SLING-5660 at 3/1/17 12:16 PM:
-----------------------------------------------------------------
If we don't add a path limitation we would need to
# invalidate the whole cache for every resource removal within {{/apps}} or
{{/libs}}, because you don't know which {{resourceType}} has just been removed
# invalidate the whole cache for every resource change within {{/apps}} or
{{/libs}}, because just retrieving the {{resourceType}} property for every
changed event would be too much effort.
That would be the same with the new observation API.
Don't you think that this would invalidate the cache too often?
was (Author: kwin):
If we don't add a path limitation we would need to
# invalidate the whole cache for every resource removal within {{/apps}} or
{{/libs}}, because you don't know which {{resourceType}} has just been removed
# invalidate the whole cache for every resource change within {{/apps}} or
{{/libs}}, because just retrieving the {{resourceType}} property for every
changed event would be too much effort.
That would be the same for observation.
Don't you think that this would invalidate the cache too often?
> Validation is using outdated sling/validation/model
> ---------------------------------------------------
>
> Key: SLING-5660
> URL: https://issues.apache.org/jira/browse/SLING-5660
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Reporter: Oliver Lietz
> Assignee: Konrad Windszus
> Fix For: Validation 1.0.0
>
>
> The new {{sling/validation/model}} (one property removed) was used only after
> restarting Validation bundles:
> {{sling.validator.missing-required-property-with-name}}, {{location}} was
> empty.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
