Portlets can be customized in so many different ways and there is so much one can do with a portlet. I don't see how anybody can abstract portlets to a level desirable for a framework. Of course, JSR-168 is a standard, so it carries some credibility. Yet, to implement it properly, you still need a base portlet class with JSR-168 extending it. After examing all the portlet API's out there, you'll probably end up with a base portlet class that simply consists of set and get content methods.
On one side, by implementing support for JSR-168, you create a unified portlet API for PHP developers everywhere (something I don't believe exists or at least isn't mainstream). On the other, you may be unfairly restricting ZF users to conform to this particular standard when there are others widely used in practice. Is it ZF's role to push one over the other? I don't know if I am in a position to answer that.
Gregory Szorc
[EMAIL PROTECTED]
P.S. To the original poster, if you are looking for a quick and dirty portlet solution, I created a simple piece of portal software you may be interested in. Source code is at http://opensource.case.edu/svn/start/trunk, minimal docs at http://opensource.case.edu/projects/start and demo at http://start.case.edu
On 9/21/06, Willie Alberty <
[EMAIL PROTECTED]> wrote:
I'm currently developing an application which has some CMS- or portal-
like features. While doing some research for the API design, I
discovered a Java standard called "JSR-168 Portlet API 1.0" <http://
jcp.org/en/jsr/detail?id=168 > which defines a standard extensible API
for portlets.
I think I'm going to adapt this API for my project, but wondered if
it would be of interest to others. Thoughts?
--
Willie Alberty, Owner
Spenlen Media
[EMAIL PROTECTED]
http://www.spenlen.com/
