> Hi Remy,
>
> That would be great to be able to set a default for a Namespace/role
> combination as you suggested. That would solve all the issues I'm facing.
>
> Just throwing some ideas around,
>
> I was thinking that a property could be made 'inheritable', the ObjectNode
> can check its parent when its created and inherit its properties. But I
> think this would be of limited appeal to users and could raise more
problems
> that it solves.
Indeed, that may be tricky to use.
> Another approach might be to make it pluggable with classes, where a user
> could write a class to generate the properties. This would be the most
> flexible solution. For example,
>
> class TimePropertyGenerator extends SlidePropertyGenerator {
> public NodeProperty generateProperty() {
> return new NodeProperty("getlastmodified", new Date(), true);
> }
> }
>
> Problem with this is that the signature for generateProperty() would need
to
> be decided on, looking at the PutMethod source there are a few parameters
> that would be needed, the SubjectNode and the HttpServletRequest object.
(To
> determine the content type and content length, etc).
Actually, I was thinking about something like that for property validation
(to allow control of the properties after going through the WebDAV layer).
Remy
