Thanks for your response Sean. That all makes sense. We have a couple of other components that directly interact with the repository and understand our content model (hence the question).
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. Regards, Shaun. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Sent: 16 October 2006 14:49 To: [email protected] Subject: Re: [magnolia-user] Using Custom Content Types with Magnolia Hi Shaun, >From my experience, Magnolia pretty much likes to use its own custom content types. Therefore, if you're trying to use the JCR as a point of integration with other applications, it may be rough going. If, on the other hand, you're managing these data with Magnolia exclusively, it's pretty easy to set up a Dialog definition that specifies what data should be captured for a particular kind of content. These data are still stored in the JCR as mgnl:*, but Magnolia has a concept of what they are and how to work with them. For example, you can say your page template is "foo". As part of that template definition, you can specify that it should only include paragraphs (or a single paragraph) of type "bar". Type bar may include a start date, end date, summary, keywords, and text, for example. Thus, it's not quite what you describe, but may be able to give you something pretty similar. Hope that helps, Sean On 10/14/06 6:00 AM, "Shaun Barriball" <[email protected]> wrote: > Hi all, > Magnolia provides a feature rich interface for managing JCR 170 based > content. Based on a review of RC3 it uses a handful of custom content > types currently including: > > * mgnl:content > * mgnl:contentNode > * mgnl:metaData > > We have an established more strongly-typed content model we'd like to > manage, potentially using Magnolia. > > Has anyone used Magnolia with other custom content types created to > model a particular problem domain e.g.? > > * acme:fooBarPage content type > > If not, is it feasible to use Magnolia for custom content types or is > the CMS fundamentally based on the mgnl:* types? > > All comments appreciated. > Regards, > Shaun. > > PS> Well done to the team for getting RC3 released. > > Send instant messages to your online friends > http://uk.messenger.yahoo.com > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/magnolia/developer.html > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- Send instant messages to your online friends http://uk.messenger.yahoo.com ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
