Hi Zheng,
I'd like to collaborate on the Admin portlets for Pluto 1.1 too. I like the command pattern that you used in your first try at admin portlets for Pluto 1.1. The only change I'd like is too add role-based security by checking security-role-ref in portlet.xml and doing a PortletRequest.isUserInRole() check before control is passed to the action.
Here are my minimum requirements for admin portlets:
1. File upload and war deployment into webapps directory.
a. Modify web.xml and Pluto configuration files as necessary
2. Ability to undeploy portlets by removing configurations and deleting deployments.
3. Ability to configure and change layout of a portlet application.
We should also plan for the administration of authenticated users and user information attributes (PLT.17) in the admin console.
/Craig
| Zhong ZHENG <[EMAIL PROTECTED]>
09/03/2005 01:12 PM
|
|
Hi there,
Since you have made some modifications on the Pluto Driver subproject, the previous Pluto Admin did not work any more. So I am thinking of refactoring the admin app:
1. Provide a pluto-independent Struts-like MVC framework for portlet. I don't know whether Struts supports portlet currently, but I think it not necessary to require Struts to run the admin. I can write a very simple yet not full-featured MVC framework based on which I may facilitate the admin development.
2. Separate the pluto portal driver dependent codes into a single package. Since Pluto 1.1 is still on development, there will probably be midifications on the portal driver. So separating the dependent code will make it easier to meet the future need.
I'd like to collaborate with you on the admin app. So what you think about the refactoring plan?
Regards.
--
ZHENG Zhong
heavyzheng {AT} gmail {D0T} com
http://heavyz.sourceforge.net
