I, (in the past and now as well) have a need for a "light weight" portal
solution. This light weight portal solution is basically an
"aggregation server". I consider it more like a simple wrapper around
the portlet container. It provides the following:
1) Ability to invoke portlets and include their content into a webapp in
a compliant manner.
2) Ability to manage a "portlet registry" at runtime.
3) Ability to define a "page" or grouping of portlets at runtime but
have no layout associated with it.
4) Ability to customize rendering using different technologies (simple
jsp, a servlet, velocity, etc. . .) without having to jump through
hoops. Custom tags to insert rendering such as the <pluto:render> tag
would be nice.
5) Ability to have a portable solution which can be packaged as a single
war (not built differently for different environments) and deployed on
any compliant servlet container.
There may be one or two additional requirements that I'm not thinking of
right now, but literally, this is a very simple portal solution and
needs to be void of additional "fluff". The solution does not need to
include any other "value added" services - and it would be a pretty big
negative if it did.
I have been developing this solution in Pluto, however, at apachecon, I
got wind of the fact that some people may not be comfortable with this
and would prefer that the test driver does not include things such as #2
and #3 above (and perhaps others). The solution needs to be of
production strength.
Would others please provide their ideas on where the best place for this
solution is, whether it may be provided in a solution we allready have
(besides the pluto portal in question), and how we should move forward?
Thanks,
David
