[
https://issues.apache.org/jira/browse/SLING-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890360#comment-15890360
]
Konrad Windszus edited comment on SLING-5660 at 3/1/17 3:33 PM:
----------------------------------------------------------------
2. cannot be improved although the resource type of the added/modified resource
is always sent with each event, because the validation models are built from a
complex hierarchy of resources where some of them might have arbitrary
{{resourceTypes}}. Just think about a validation model where only a new
{{children/additionalresource}} is added with a
resourceType=jcr:primaryType=nt:unstructured.
I will prepare a fix though which for now always invalidates the cache. I am
still not 100% convinced that this is a wise choice, but having a limitation in
terms of paths for valdiation models I don't like either.
was (Author: kwin):
Actually 2. can be improved, because the resourceType is anyways sent with each
{{SlingConstants.TOPIC_RESOURCE_CHANGED}} event, so only removing resources
would requires us to always flush the full cache. Shouldn't happen too often
though. I will prepare a fix with the improved cache invalidation.
> 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)