Anyone opposed to applying SLING-864? (was: Selectors on non existent resources)

2009-07-06 Thread Bertrand Delacretaz
On Mon, Jul 6, 2009 at 2:13 PM, Ian Boston wrote: > On 6 Jul 2009, at 11:01, Alexander Klimetschek wrote: >> ...See this (still open) bug with a patch to add selector support: >> https://issues.apache.org/jira/browse/SLING-864 > > I see, same issue > I guess since its been there since 2.0.2, its no

Re: Anyone opposed to applying SLING-864? (was: Selectors on non existent resources)

2009-07-06 Thread Alexander Klimetschek
On Mon, Jul 6, 2009 at 3:29 PM, Bertrand Delacretaz wrote: > On Mon, Jul 6, 2009 at 2:13 PM, Ian Boston wrote: >> On 6 Jul 2009, at 11:01, Alexander Klimetschek wrote: >>> ...See this (still open) bug with a patch to add selector support: >>> https://issues.apache.org/jira/browse/SLING-864 >> >> I

Re: Anyone opposed to applying SLING-864? (was: Selectors on non existent resources)

2009-07-06 Thread Tobias Bocanegra
On Mon, Jul 6, 2009 at 3:59 PM, Alexander Klimetschek wrote: > On Mon, Jul 6, 2009 at 3:29 PM, Bertrand > Delacretaz wrote: >> On Mon, Jul 6, 2009 at 2:13 PM, Ian Boston wrote: >>> On 6 Jul 2009, at 11:01, Alexander Klimetschek wrote: ...See this (still open) bug with a patch to add selector s

Re: Anyone opposed to applying SLING-864? (was: Selectors on non existent resources)

2009-07-06 Thread Alexander Klimetschek
On Mon, Jul 6, 2009 at 6:20 PM, Tobias Bocanegra wrote: > if the selectors 'catch' they should not be included in the path. > rather assume a non-existing resource > at /content/some/path/foo. the script can still assemble the full path > by concatenating all selectors and extensions. > > is there