Re: VanityPath and ResourceResolver#map

2016-12-16 Thread Felix Meschberger
Hi > Am 16.12.2016 um 13:22 schrieb Carsten Ziegeler : > > Justin Edelson wrote >> Hi, >> IIUC, this is by design. Vanity paths are intended for inbound use only. >> > > Right, they might not be as "stable" as a mapping, e.g /latestnews might > point to page A now, but to page B in three hours.

Re: VanityPath and ResourceResolver#map

2016-12-16 Thread Carsten Ziegeler
Justin Edelson wrote > Hi, > IIUC, this is by design. Vanity paths are intended for inbound use only. > Right, they might not be as "stable" as a mapping, e.g /latestnews might point to page A now, but to page B in three hours. Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@a

Re: VanityPath and ResourceResolver#map

2016-12-16 Thread Justin Edelson
Hi, IIUC, this is by design. Vanity paths are intended for inbound use only. Regards, Justin On Fri, Dec 16, 2016 at 4:57 AM Antonio Sanso wrote: > hi *, > > I would have a question about VanityPath and ResourceResolver#map . > Assuming I have a resource /content/foo/bar with a van

VanityPath and ResourceResolver#map

2016-12-16 Thread Antonio Sanso
hi *, I would have a question about VanityPath and ResourceResolver#map . Assuming I have a resource /content/foo/bar with a vanity path set ti /bar . AFAICS if I try to do ResourceResolver#map("/content/foo/bar”) the expectation give by the ResourceResolver#map API would be that this