Dec 8, 2008 JSR 286 vs JSR 168 Features JSR 168 Specification Only supported within the same

e portlet application using session attributes Target portlets will only "see" messages during next render request. JSR 286 Specification Add additional coordination capabilities Limited only to String Values. Sharing of session data beyond the current Portlet application. Sharing of render parameters across portlets.

Inter Portlet Communication

Life cycle

Portlet Filters

Caching

Common Web Frameworks

Portlets cannot update their state during a render New 3rd life cycle phase before request: "event" handling rendering not really possible Supports Allow on the fly transformations of information in both the request to and the response Doesn't Support from the portlet Defined in portlet.xml Extended Cache support. Allow public cached content for multiple users Extended Cache support. Allow public cached content Servlet dispatching for multiple users. not supported from Improved support for web process Action. frameworks (Struts, JSF, Spring) Needs Portals Allow servlet dispatching during all Bridges or similar lifecycle calls: processAction, solutions. processEvent, render, JSTL support very serverResource. limited Extended JSP tag library <defineObjects/>, support for JSF

Non HTML Resources(pdf,

A portlet can only

doc, images etc.)

render html fragments. Have to fallback/delegate to the servlet container. Requires coordination between portlet and servlet.

Difference between JSR 168 and JSR 286

JSR 168 VS JSR 286 There are Major and Minor Improvements in JSR 286 while compare with JST 168 Major Improvements :-

*. Events Handling enabling a portlet to send and receive events and perform state changes or send further events as a result of processing an event. *. Public render parameters ( Shared Parameters) allowing portlets to share parameters with other portlets.
*. Resource serving (Resource Addressing) provides the ability for a portlet to serve a resource

*. Portlet filter allowing on -the -fly transformations of information in both the request to and the response from a portlet.
Minor Improvemetns :-

getNamespace() this method gives unique value for the portlet window getWindowsID()- this method returns portlet window ID Portlet Cookies- Can beset on particular phase and retrieved on the subsequest phase Additions to PortletRequestDispatcher Portlet container runtime options