I continue to believe that the Portlet idea in practice should simply implement the controller paradigm of the MVC instead of being some class that needs extending by the typical web developer just to create a html fragment. Just like servlets are best served by something like Struts, I believe portlets are best served by something like the MVCPorlet idea. There should be a config file that ties actions/events to views, which the controller (portlet) uses to render it's fragment.
Maybe the J2 core doesn't deal with that, only providing a container for JSR 168, but as a portal implementation it will have to deal with this idea sooner or later to reach maturity imho since web applications are almost universally seeking the MVC paradigm going forward.
Thoughts?
%regards -tk
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
