"dhartford" wrote : anonymous wrote : 2) CMS control - it would be cool if you could deploy a single (or clustered) CMS "server" and deploy content links as required to all instances of portal via ON. this might be a bit bloated, not sure of implications and whether portal could fully handle it. | | Seperating out the CMS "server"/repo would definately help, not only for jboss portal but also as a seperate file-repository to develop against (aka WebDAV/JCR repo for other than just portal-CMS). | | It would be great to deploy a 'Jboss Repo' that stores the CMS content and have the jboss-portal upgrades be seperated/less dependent of the repo. Could also setup CMS-bundles that are added to the repo and point to them from jboss-portal. I am not sure to get this right, the "CMS server" is already quite independent (it is JackRabbit) with a homebrew Hibernate storage. This could be interesting to discuss over the phone during a conf call. I am not even sure you and jewhit are talking about the exact same thing. Please email me if you are interested by a call, same for jewhit. anonymous wrote : As another item, would be nice to have seperate administration/backup functionality that is domain-knowledge-specific to the repository versus the portal (i.e. portal admins deal with portal stuff, storage admins deal with storage stuff). Ok, the underlying thing is to add the notion of group i guess (on top of user/role), we already talked about it and it is something that we need to allow. anonymous wrote : | my two coppers, | -D They worth a dime ;) Thanks for your input View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972837#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...