[jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-721) Formalize the contract between the core and the layout

Formalize the contract between the core and the layout ------------------------------------------------------ Key: JBPORTAL-721 URL: http://jira.jboss.com/jira/browse/JBPORTAL-721 Project: JBoss Portal Issue Type: Task Security Level: Public(Everyone can see) Components: Portal Theme Affects Versions: 2.4 Final, 2.6 Final Reporter: Julien Viet Fix For: 2.6 Final * introduce a Servlet like Layout API with life cycle methods like init and destroy * individual layout artifacts like the layout, a region, a window, etc. all inherit from a common interface * the common interface exposes a generic render method that takes a context as argument * the context contains the markup fragments from the individual portlets with their allowed actions (per family, like 'modes' and 'states') * this allows for more fine grained rendering of the markup (render only one region, one window,...) * perhaps create hierarchie in the layout API (page, region, window) * add resource bundle for layouts * introduce layout meta data (from the descriptor) and provide it at initialization time as an info object (analogous to getInfo() in servlet) * think about dynamic layouts (perhaps metadata is not that static ?) ???? * window properties like 'no decoration' as part of the meta data * architect this new API in such a way that there is no tie to JSPs or Servlets and the request dispatcher (those should only be implementation details of the default layout) * in the core, add a portal aggregation command to create the final markup (using the new layout API)