The major changes are: - In addition to the action and render phases, there's a new "event" phase where portlets can communicate. These events are subscribed and published using some sort of QName/XML naming feature, and receiving the events happen between the action and render phase. - A portlet can now serve resources with resource requests. This (probably) means that portlets can generate binary content, and benefit from the portal server authentication/authorization mechanism. If I have understood this feature correctly, it means that several more of the result types can be supported. - Portlet filter support, which means we can add support for things like SiteMesh, if someone needs that (although SiteMesh and the portal server itself kind of overlaps...) - Public render parameters that is a "lightweight" form of portlet communication. - Some annotations supported for marking portlet methods as lifecycle methods.
Nils-H On 8/12/07, James Holmes <[EMAIL PROTECTED]> wrote: > I haven't studied the new portlet 2.0 spec much yet, but I'm wondering what > sort of changes we'll need to make to the Struts 2 portlet plugin to support > it. > > Just something to think about. > > James > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
