Hi Alex, Alexander Klimetschek schrieb: > On Fri, Nov 21, 2008 at 12:34 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: >> You set an absolute path in the property. If the request URL cannot be >> resolved, a query is run which asks for a sling:vanityPath property set >> to the request URL path (actually HttpServletRequest.getPathInfo()). If >> found the resource either used directly or a redirect is sent back to >> the client if the sling:redirect property is set to true. > > So there is no difference between "vanity urls" and "vanity paths" (in > the current sling)?
Ehrm, yes. And this is mostly historic: VanityURLs are configured for the ResourceResolver and is a straight mapping applied before starting to resolve a resource. Its just like: is there a mapping, then apply it. Vanity Paths only came recently (not included in jcr/resource 2.0.2, IIRC) and come as a last resort if the request URL could not be resolved otherwise. This is of course confusing, and by redefining the sling:vanityPath property (used for the latter, search-based approach currently) we can also cope with all other use cases we currently handle by configuration much easier. Regards Felix
