Maverick doesn't support it in the same way as Turbine, but you have full use of the Velocity template engine. You might have a look at the Velocity Layout servlet, for example.
Another approach would be to setup a template controller of your own and pass the names of the main, navigational, and page templates as parameters. The controller could forward to the main template and pass the other parameters in the model bean. So that the Velocity template might look something like:
<html> <body> #parse($model.topnav) #parse($model.page) #parse($model.btmnav) </body> </html>
and the template controller might be setup like
<command ... >
<controller ... >
<param name="topnav" value="/pages/topnav.vm" />
<param name="btmnav" value="/pages/btmnav.vm" />
</controller><view path="/page/myPage.vm" />
</command>
Though, it might be better to use a View element rather than a Controller, but the same strategy woudl apply.
A whole 'nother approach I'd like to try myself (that other people already do) is to use XLS to generate the Velocity templates. That way you could end up with a valid XHTML file that Tidy can validate :)
HTH, Ted.
Leandro Rodrigo Saad Cruz wrote:
Hi all. I've been using turbine for a long time now and I want to experiment with maverick !
One thing I really like about turbine is the way we structure the page that is sent to the user. In turbine can use a structure like this :
- render the main screen template - render navigational templates - render the page merging all this templates using a layout template
Is it possible to do it with maverick ?
------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ [INVALID FOOTER]
