BaseBeanPortlet

[Andrew Petro]

Rather than implementing BaseBeanPortlet in terms of a template method for
getting the name of the Spring-managed-bean actually implementing the
portlet, would it be preferable for it to read a portlet init parameter for
the name of the Portlet bean to which it should delegate?

"PortletToBeanProxy", to take a page from Acegi's FilterToBeanProxy.

http://www.acegisecurity.org/multiproject/acegi-security/apidocs/org/acegise
curity/util/FilterToBeanProxy.html

For instance, GenericXsltPortlet as implemented provides for one specific
bean location coded as a static field in Java. Adopting a generic
InitParamBeanPortlet approach would allow multiple realization of the
GenericXsltBean with different <portlet> entries delegating to differently
configured beans.

Hard coded bean paths/names in the .java seems undesirable and doesn't buy
anything -- putting this in the portlet.xml declarative configuration seems
equally expressive and more flexible.

Andrew

------------------------------------
Unicon, Inc.
Andrew William Petro
Software Developer
ape...@unicon.net
3140 N. Arizona Ave
Suite 113
Chandler, AZ 85225
mobile: 203.915.7333
------------------------------------

[Eric Dalquist]

The end goal is to do away with this code and just use the spring provided portlet MVC code. There is a JIRA issue for this task.

-Eric

--
-----
Fight back spam! Download the Blue Frog.
http://www.bluesecurity.com/register/s?user=ZXJpYy5kYWxxdWlzdDEyOTQ%3D