Hi Ian In fact I rewrote a Sling integration test just this morning exactly doing such property setting for verification purposes (the test used to check the rep:principalName property which is not available as such any longer).
Regards Felix Ian Boston schrieb: > Angela, > Fantastic, > I misread the patch forgetting that * might be allowed. > Thank you. > Ian > > On 3 Dec 2009, at 17:44, Angela Schreiber wrote: > >> hi ian >> >> JCR-1984 addressed a problem that protected properties defined >> by the user/group node types were exposed by the #getPropertyNames >> and #getProperty methods, although they could not be modified >> by the corresponding set/remove methods. >> >> this issue should not affect additional, application specific >> properties that were or will be stored with a user/group. >> the nodetype still allows for >> >> - * (UNDEFINED) >> - * (UNDEFINED) multiple >> >> and those props should be exposed by the mentioned methods. >> i'm not aware of any change that would have broken this. >> >> angela >> >> >> >> Ian Boston wrote: >>> Hi, >>> IIUC [1], post 1.6 blocks an authorizable node from holding any >>> properties, other than those listed in the schema. >>> How do I add and retrieve a well defined set of properties for the >>> node as was possible in JR15 ? >>> We have an application that stores extra group and user metadata on >>> the authorizable node and I really don't want to have to rewrite it. >>> Thanks >>> Ian >>> 1 https://issues.apache.org/jira/browse/JCR-1984 >> > >
