I am always wonder why people suffer but still taking the wrong tools for the job. Navigation portlet should provide navigation data and _must_ have separated presentation. And for presentation there is a perfect candidate - language that designed to transform data into whatever you want - xsl. (not Velocity that is a perfect for templating but ugly for transforming)
So a simple scenario: Navigation portlet produce XML with navigation components, preferences, etc. watever you want. After it wrapped up with renderer (xslt transformation) that will produce an output. Here it can accomodate even Velocity renderer. But the point is : Since this scenario has a well defined separation of business logic (obtaining portal navigation data) from presentation (construction of html havigation fragment) you can acheve almost any look and feel that you might want. A simple example of right approach: I want to have my navigation in flash. How can I achieve it ? With separated presentation layer - easy. With current implementation - it's scare me. Anyway I have to write proper navigation portlet for my portal ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926872#3926872 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3926872 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
