OK, that kinda makes sense, but does seem to mean the setTitle() method on the MetaData class is redundant, as it would never be used by anything. I had assumed that as the method was there, it would do something useful :-)
Dealing with the wider issue of how such data is stored, I think it would make more sense if all these values were accessed via one logical API, as they are all logically metadata elements, regardless of how they are physically stored in the repository. That's how I'd assumed it was supposed to be working, hence why I thought there was a bug. What do others think about that? Thanks, Simon On 14/09/06, David Smith <[email protected]> wrote:
This question should probably be on the magnolia-users list instead, but besides that.... I believe if you are talking about the page title (displayed in adminCentral on the second column), that is a NodeData object, not a MetaData. As far as I know this is not a bug. It's that way so the dialogs can access it similar to nav title, content title, etc., ... --David Simon Goodchild wrote: > Hi Devs, > > I've been experimenting with automated page creation via the APIs, and > think I've found a bug in the MetaData class. I'm using 3.0RC2. > > The symptoms I'm getting are that although I can create the page and > set properties like the template using the MetaData class > implementation, I cannot set the 'title' property using > MetaData.setTitle(). From analysing the behaviour of which properties > work and which don't via the JCR Browser, the difference seems to be > that 'title' is stored as a subnode of the content node by the admin > interface, whereas template etc. are properties of the content node > itself. It seems like the MetaData class implementation doesn't take > account of this, and tries to store everything as a property of the > content node. > > I wanted to make sure this was actually a bug (and I'm not just doing > something stupid!) before logging it in JIRA. I'm happy to make the > changes to MetaData if someone can point me towards an example of how > to create a subnode like this. > > Thanks, > > Simon > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/magnolia/developer.html > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
