"PMN" wrote : | deployment: | It is currently provided through xml descriptors, some info are persisted, others are not. Why is that? At every start the entire xml descriptors are read and it is not clear what is persisted, when changes are detected, nor even if the xml descriptors are consistent. As a consequence there is no real design for extension or customization. Is there any future plan on this topic? | portlet.xml is a deployment descriptor. portlet-instances and *-objects are just here for people willing to pre-populate the portal objects (instead of using the admin portet or as compliment). The portal structure needs to be persisted. "PMN" wrote : | layout: | Layout assignment is done through xml descriptor. That is a bit rigid compare to the ability to dynamically associate a layout to a page through the event mecanism for example. Any plan to improve it? | Not sure i understand the question. You can change the layout programatically. "PMN" wrote : | platform / solutions: | A few features are "solutions" rather than platform building blocks - themes, navigation and dashboard injection. Any plan toward a clearer separation? | Yes, but note that core is already the glueing part. Some parts should be exported though. anonymous wrote : | theme: | Any plan toward an integration with YUI ? | No, but better plans ;) See the presentation framework discussions. GWT comes in mind as an example of presentation framework usage. It will be part of JBoss Portal 2.8 anonymous wrote : | These are just genuine questions, please do not see any criticism where there are not. Good questions, please see the presentation framework discussions and see if you have ideas to bring on the table, a lot of the work has already been done but it's always interesting to see in users use-cases fit in the model. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130510#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...