best way to describe page structure

[w2ttsy]

I am in the process of building a web app using Spring 3.0 and would like to know the best way to describe page structure.

in the previous framework i used, a site was made up of page objects in a singleton pattern and using a forward facing controller.
each page object had a name (which was transformed into a search friendly URL), a key for referencing the page object via the JSP and some other parameters.

now the most important part is that a collection of these objects were loaded into a map, and then the map could be iterated over to define site maps, relationships between child and parent pages and provide navigation trees. The best part is that I could access properties using the lookups provided.

now that i've moved to spring, I have a set of controllers mapped via annotations. Now each controller has a view and a model attached to it.

How should I go about assigning things like page titles or other properties? for instance a reference to a section in a CMS. I was thinking of adding it as a property to my annotation, but that seems a little dirty.

Also, what would be the best way to establish parent/child relationships or iterate over a list of controllers, I dont really feel like hard coding my links in each view.

some advice would be good. Have i completely missed the mark here?

[nrganeshbabu]

just curious...why did you move to spring...any compelling reason? what was your previous framework?