On 12.10.2012, at 09:27, Dimitar Dimitrov <[email protected]> wrote:
> But from now I have a need of user defined types which then will be > managed by filtering and transforming to other structures. Exactly for > the filtering needs I should now the type primary type of the nodes. > Then these nodes will be transformed to visual component in the Flex > based interface. For that I need of object persistence also, but I have > not implemented yet, because of asynchronous nature of the Sling CRUD. Use properties to "mark" your types, and using sling:resourceType for that is usually the best way to go, as you get Sling's flexible rendering for free. Properties can be updated, easily searched for, replaced over time with a new way if it comes up, you can use additional properties for "sub types" etc. You don't get any constraints this way, but encoding application/ui constraints into the storage layer is usually not a good idea, as these change over time. Hence it's best to put them in the application layer. HTH, Alex
