I think you can do what you want. Write your portlets (chat, file repos, etc) and then package a custom portal with the "admin" stuff disabled.
See my JBossWorld presentation on creating a custom portal, that might give you some ideas on what you could do.
Packaging a portlet is very similar to a standard JavaEE web app, except it includes a portlet.xml (in addition to the standard web.xml).
Typically portlets are packaged as WAR files, the structure of which is defined by JSR168 / 286: http://jcp.org/en/jsr/detail?id=286
I recommend giving the spec(s) a read to help you move along; good luck!
It's not the portlet packaging which dazed me, but more the portal packaging. A bundle with portlets, themes, layout, sso, etc.
After reading Peter presentation, I think I'm able to package my application as an EAR which will contains portlets and themes and then use scripts to update the principal SAR (commonly jboss-portal) tu use my embedded themes and to remove unwanted features.
Peter, thank you for your presentation
Thanks for help
I'm almost happy of my application building within JBoss portal but I encounter a somewhat complicated problem. I want to use a ThirdParty application which will embed the Authentication business. This Application is a sort of SSO handler with a backoffice application where we can add User And Role.
I can successfully authenticated myself thanks to a JAAS LoginModule available for this application, but the portal failed if the User is registered with another Role than Admin or User and I can't see any exception in the log file.