Re: refactoration of Pluto Admin 1.1

[Zhong ZHENG]

Hi,

I enjoy the discussion with you. Here are some points I summarized from the conversation:

1. Using the command pattern to implement the admin app is preferred. In this way we do not need some external dependencies. The patch I submitted to JIRA contains a framework designed for the admin app. Maybe that is too complicated and shoud be simplified?

2. As Craig said, whether to have the admin app as a separate webapp or incorporated into the Pluto's portal is a thorny issue. David proposed to implement the deployment within the portal and provide a mechanism for connecting to the portal and sending the deploy/undeploy commands, in order to allow multiple interfaces to the functionality. I like that idea.

3. The admin app implementation should not be bound to a single servlet container (Tomcat). The cross context issue (and binding portlet session to servlet context) needs to be fixed for Pluto 1.1.

4. Some new features should be added to the admin app, including the administration of authenticated users, user information attributes, and portal layout management.

Mmm... the admin app seems to be a very interesting mission. :-)

Thanks to all of you for your advice.

Regards.

--

ZHENG Zhong

1 Avenue Alphand
75116 Paris, France
+33 6 76 80 45 90

heavyzheng {AT} gmail {D0T} com

http://heavyz.sourceforge.net
http://heavyz.blogspot.com
http://spaces.msn.com/members/zhengzhong