Catalina, My understanding is that the cms:setNode directive just exposes whatever properties are attached to the page in the repository already -- that is, it doesn't know what *should* be there, it just makes available whatever already is. (You can see what properties are actually set using the "JCR Browser" tool.)
The paragraph attribute of the mainBar directive helps determine what properties *should* be there and what UI to show for them. There may be more already set than what the paragraph specifies, but you'll only see a User Interface for those specified by the paragraph. So, the first time you look at a page, cms:setNode will make nothing available, because nothing has been set in the repository yet. When you click the "properties" button, a UI will be generated according to the paragraph definition. When you enter data and click "Save", those data are persisted to the repository. Then, the next time you load the page, cms:setNode peeks in the repository, sees the data, and makes them available to the rest of your JSP. Hope that helps a bit. Sean On 8/28/06 10:06 AM, "Catalina" <[email protected]> wrote: > > Hello Magnoliens :-) > > I'm wondering how does a page know which page-properties to use. In the > tutorial, the quickstartPageProperties are not connected to the > quickstart-Template. The only place where I found a mapping is in the > main.jsp: <cms:mainBar paragraph="quickstartPageProperties" /> > But <cms:setNode var="pageProperties" /> knows exactly which node to use. > (although it is two lines above the cms:mainBar-tag) > Is cms:mainBar setting the property for the page? Or is there same magic > happening, maybe a naming convention? > > Hoping for enlightenment > Catalina ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
