Retaining default Portal implementation and customizing a ne

[babsmk]

I am looking at a way where i can define\create a new portal instance with CMS, Personalization, Themes & Layouts , authentication all to have modified functionality than what Portal offers by default.

Essentially i would need instances of CMS and other Portlets which can be modified for my Portal instance. At the same time i want to retain the default functionality offered by JBoss Portal. i.e. have a means to retain exiting default functionality intact so that it can be used for any other new portal created.

I have read topic http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121025 which explains ways to have another object.xml created. Can custom xml be put in the same conf folder in portal.sar . How do i create the customized JBoss portlets and attach them to this.

Any help is appreciated.

[peterj]

I would suggest just editing the existing data/conf/default-object.xml file. If you include your *.war files within jboss-portal.sar, you can reference your portlets from within there. Or you can define your portlet locations within your own *-object.xml file.

If I read your question correctly, I think what you are asking is if you can add a second *-object.xml file to data/conf. Well, when you did it, what happened?