here are some other thoughts I gathered in the document in our repository: Presentation layout: | * Layout is a service fully managed by the presentation client. | * Any state related to the presentation model is managed by the presentation in an opaque manner | o The presentation server cannot interpret the state. | o The state life cycle is dependent on the subset of the model it is attached to. | So here we are really focusing on laying out window and how to manage the state associated to it, probably that my previous posts are a bit confusing as they reference existing framework. There will be several implementations of the presentation client using various technologies (classic and ajax), so we cannot really adopt any framework for all, however we can rely on one framework capabilities to express the layout system (although it can be a best effort). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106938#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...