Inheriting from the mgnl:* types won't get you much from Magnolia for free. For example if you inherit from mgnl:content and write nodes of your subtype to the website repository, they won't be treated by Magnolia as though they are mgnl:content nodes. And yes for activation there are dependencies on the MetaData node of a content node. For example you won't see them in the JCR Browser or the website view. Much of the logic is dependent on the name of the primary type of a node, rather than the type itself.
Nonetheless, it is relatively easy to use your own types in your own module. The workflow module is one example of this. Am Montag, 16. Oktober 2006 15:58 schrieb Shaun Barriball: > I'm guessing inheriting from the mgnl:* types isn't going to help much as > Magnolia really wants to use its own weakly typed structures - Meta object > etc. ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
