Hi Richard, Thanks for the detailed reply, it's certainly given me some pointers to look into.
Can I ask what you mean by "We then create one or more magnolia "Model-Classes""? I'm expecting to develop a magnolia module which will contain a new basic POJO model, an interface wrapper layer to my web services and of course my template definitions (in Freemarker as opposed to JSP is my preference). I'm looking at the Magnolia Blossom samples and this I think will give me that. What module/API are you developing to? Ideally I want to deliver components and area definitions in my module, and allow content definers to create their pages and choose where they place my components/areas on their page. I also need to consider how different clients may want to render the POJO model differently. My initial idea is that upon login, I will retrieve the complete POJO model for that person (i.e. make all retrieve web service calls). So as the user nagivates the different pages, I just access the different sections of the POJO model. I will only make a web service call if the user updates some part of the model or I need to refresh. Regards, Paul -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=2e16ec5c-2be3-4d9a-b79d-f6df9f2bc0bd ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
