In effect what you are saying is correct with one exception: I want to be able to add/remove portlets from the portal at runtime so that joe-normal-user would not even see the admin portlet.
Use case scenario: Dr. Researcher has technicians working for him who are neanderthals, so they are not to see anything other than a screen that allows them to enter incoming blood sample barcodes. In this case, they do not see *anything* else (i.e. no portlet window decorations at all) other than the DataEntryPortlet in their browser after logging into the web application. Conversely, Dr. Researcher wants the ability to add and remove technicians from the system, as well as modify the supported barcode types used by incoming tissue samples so he would have full access to the BarcodeSupportPortlet and the UserPortlet, as well as the DataEntryPortlet. Taking it even a step further, Mr. Admin may need the ability to reconfigure portlet availability if suddenly there becomes a Super Technician role versus just the plain vanilla Technician role, in which case the Super Techs also get access to the BarcodeSupportPortlet. Essentially what I am asking for is run-time portal configuration as opposed to design-time configurations. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912729#3912729 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912729 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
