Hi Bertrand, Am Montag, den 17.12.2007, 10:04 +0100 schrieb Bertrand Delacretaz: > I like the idea, though if we want this in microsling we'll need some > configuration mechanism (which could be part of the autoexec script > mentioned above).
Hmm, such configuration would probably be placed in the web.xml file. > > The problem is, that it was once decided, that properties would never be > > addressed directly ... > > I know, but why not give access to them, at least for the GET method? > We have a use case with the textarea/iframe initialization. Not against providing properties, just want to remind :-) > > ...I would solve this problem such that the resource resolver would (a) > > accept addressed properties and (b) the resource type of the property > > resource is the resource type of the parent node. Of course a property > > resource would return the property and not the parent node.... > > Sounds reasonable, and people can always add an extra selector to the > Property URL to use a different script. Yes, or the resource type could be the resource type of the parent node plus the property name. For example for the jcr:data property of an nt:resource node, the resource type could be "nt:resource/jcr:data" hence the script path would be "nt/resource/jcr/data. Alternatively the colon in the property name could be encoded before using, such as jcr_data to get "nt:resource/jcr_data". Regards Felix
