----- "Sean Radford" <[email protected]> a écrit : > Hi, > > I think I already know the answer to this question is no, but thought > > I'd ask it anyway. > > Is there are way to define a simple 'collection' type property for a > Directory? e.g. a simple StringList but where the list of Stings does > > not represent a lookup into another Directory. Or to put it another > way, > a 2-table one-to-many relationship with a foreign key constraint from > > the child to the parent.
Directories are a simple common abstraction that shares the common denominators with LDAP lookups and SQL tables to query external corporate servers (mainly for users and groups bu also for simple vocabularies). They were never meant to store complex objects. Depending on what you store in you directory it is often more sensible to use dedicated document types in a hidden folder at the root of the repository for instance. Then you will benefit from the access rights systems of the core, with complex XML schema types supports and full search engine support that directories cannot provide. If you need the full power of relational modeling they you can also define your own JPA annotated classes independently of the nuxeo specific API. -- Olivier _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
