Changing Window mode and state is possible through the NavigationnalContext which is accessible on PortalEvents by context.getPortalRuntimeContext().getNavigationalStateContext() It should be possible at the same time to change Layout (it is actually indirectly done when setting the window state) thus the architecture is articulated to allow changing of layouts. Within a layout there are regions known by names and IDs so again it should be possible to change regions. It is already articulated like that because if a window is associated to a region that is not in the layout, then the window is not rendered. This support the view of a layout as a recursive combination of lines and columns, with a simple pattern of division of columns (1/4,1/3,1/2,2/3,3/4) and see a page as defined place holders named regions. This is what is missing the most to have a great applicative user experience and I believe that what is exposed is powerful enough and easy to make. Naïve question? is there a way of doing that with 2.6 ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101578#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...