Hi Lenya devs, just a heads-up to keep you up to date:
I pushed the meta data handling down from the publication API layer (Document) to the repository layer (o.a.l.cms.repository.Node). This allows custom meta data managers for repository implementations. A small change to the MetaDataManager was required, which returns now MetaData objects (this allows custom implementations of the meta data types). The document now delegates meta data handling to the corresponding repository node. The JCRSourceNode uses a JCRMetaDataManager, which stores meta data as JCR properties with the same QName as the XML-based meta data storage implementation. The properties are defined by a mixin node type (lenya:contentNode), which is assigned to all fileNodes by the LenyaJCRSourceFactory. The namespaces and node type are registered by the LenyaRepository component. We could try to move to an XML-based node type declaration mechanism which was used by Josias Thoeny and Felix Roethenbacher (I'm not yet familiar with it). Feel free to add your comments. -- Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
