[
https://issues.apache.org/jira/browse/SLING-13288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved SLING-13288.
------------------------------------
Resolution: Later
> ResourceResolver: handle "invalid" path values for Vanity Paths
> ---------------------------------------------------------------
>
> Key: SLING-13288
> URL: https://issues.apache.org/jira/browse/SLING-13288
> Project: Sling
> Issue Type: Improvement
> Reporter: Julian Reschke
> Priority: Major
>
> Seen:
> {{{}[VanityPathInitializer]
> org.apache.sling.resourceresolver.impl.mapping.VanityPathHandler vanity path
> initializer thread terminated with an exception
> org.apache.sling.resourceresolver.impl.mapping.PagedQueryIterator$QueryImplementationException:
> unexpected query result in page 0, property name 'sling:vanityPath', got '
> ', last value was '/content/bmw/marketNORDICS/bmw_se/6-serie' at
> org.apache.sling.resourceresolver.impl.mapping.PagedQueryIterator.getNext(PagedQueryIterator.java:104)
> [org.apache.sling.resourceresolver:1.12.12] at
> org.apache.sling.resourceresolver.impl.mapping.PagedQueryIterator.hasNext(PagedQueryIterator.java:135)
> [org.apache.sling.resourceresolver:1.12.12]{}}}
>
> So far, we have only ignored null paths, plus those outside the defined path
> set.
> Vanity Paths (sym-)link from an absolute path to a resource somewhere else.
> With that, I'd be surprised if anything but an absolute path will work. But
> then, what do I know?
> Proposal: define what we think is invalid (or useless) and log those values
> in a similar way we do it for aliases (collect a certain amount, and WARN log
> them after init is done).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
