STAGING ENVIRONMENT I dont really know whether this should be posted to JBoss ON or to JBoss Portal, but I find it rather an administration oriented architecture aspect. Many Web-CMS solutions offer an editorial or staging environmet as part of the production environment where you can preview changes before they go live. The JSR170 has the idea of versioning and on top of that staging is built. In my opinion, if all pages and all layouts of the portal would reside in the JCR, then it would be posible for editors to easily add new pages to the portal or move around portlets, previsualize and have an optional workflow of aproval (jBPM) and then someone with the appropiate rights would just press a "publish" button and make the changes live. Notice that here no developer is required. The editor team would just for example add a christmas offer on the homepage of the portal and link to a new page explaining the offer, all done with the current portlets available. All of this, without managing strange XML exporting and importing... the JCR already provides a versinable storage in an elegant way. Also, having the pages defined in the JCR would allow easierly to manage for example the validation of internal links inside HTML sections. Portlet preferences may be stored in the JCR too. Its all about changing the DAOs to store in JCR instead of DBs and XML files... and we get all the benefits of permision, versioning, workspaces, sibling, ,subscription to events, etc from JCR. I am missing something? Thanks for all your extraordinary products. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981552#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...