David H. DeWolf wrote: >>>> Can you describe *what* this basic portal should contain/provide for? >>>> Shouldn't we have a clear vision of its purpose before shopping >>>> around for >>>> possible features to attach to it? Otherwise it might end up not >>>> so "lightweight" >>>> any more after all. > >> >> Yes, we should. I've stated a couple of times that my vision is: >> >> 1) Portlet Registry >> 2) Aggregation >> 3) Page Management >> 4) Simple installation and deployment >> >> NO VALUE ADDED SERVICES (sso, etc. . .)
I would go a bit further than that for a production level portal, no matter how lightweight it is. Features required: -------------------- 1- Ease of install 2- Auto-deployment of Portlet applications 3- Ability to integrate page fragments in portlet WAR 4- Declarative page structure 5- Aggregation engine 6- Basic time based caching mechanism 7- Stand-alone user management 8- Declarative security 9- Admin GUI for managing user, security, pages and portlet deployment 10- Support for major servlet containers: tomcat, jetty, jboss 11- Portal admin manual Feature *not* required: ------------------------ - user level interactive layout customization - integration with external user database or authentication service - advanced caching facilities - clustering support I'll let others add their own feature list here before commenting on the technical aspect. -- Raphaël Luta - [EMAIL PROTECTED] Apache Portals - Enterprise Portal in Java http://portals.apache.org/
