Hi, I don't know the exact reasoning any more. It was a result of implementing a JcrPropertyResource. IMHO it makes sense to some extent.
Regards Felix Am 19.11.2012 um 15:24 schrieb Carsten Ziegeler: > I'm wondering why we introduced access a property of a resource > directly via a path in the first place? :) > > This is special to the jcr resource provider and is nothing which is > supported by any other resource provider. > > At the moment, I'm just curious > > Regards > Carsten > > 2012/11/19 Bertrand Delacretaz <[email protected]>: >> On Fri, Nov 16, 2012 at 10:06 PM, David G. <[email protected]> wrote: >>> Is there a way to prevent making a GET for the full path to a property >>> to NOT return the property's value: >>> >>> HTTP GET /content/site/page/jcr:content/page-property ==> "this is >>> the page property value"... >> >> If all such paths contain "jcr:content", a Filter or front-end >> blocking mechanism might help...but that depends on your overall URL >> scheme. >> >> -Bertrand > > > > -- > Carsten Ziegeler > [email protected]
