I think supporting JSR 168 can be very interesting. A lot of the enterprise portals whether from SAP, IBM and others can easily consume JSR 168 portlets. I agree with others that this shouldn't be the ZF best practice way esp. as we are planning on working on a Java Beans like component model down the road.
I really see this the same as any interoperability/integration module we might have in framework whether db, web services, etc... It's a good thing to have because it will allow people to use the ZF for Web integration. If you'd like to move forward with this I could go and snoop around some of the enterprise vendors and see if they'd like to contribute to it to make sure it's standards compliant. Andi > -----Original Message----- > From: Willie Alberty [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 21, 2006 5:41 PM > To: Zend Framework General > Subject: [fw-general] Any interest in a Zend_Portlet? > > 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/ >
