JSR-168 is a collection of Java APIs for portlet developers. There are a number of reasons to design JSR-168 portlets that adhere to the specification. Portability is an obvious benefit. Code written according to the specification will be easier to move to among portal servers. The majority of Java-based portal servers support JSR-168 portlets.
Another benefit is easier federation. Exposing JSR-168 Portlets via Web Services for Remote Portlets (WSRP) producers is easier when portlets adhere to the JSR-168 specification. WSRP provides a standard to federate portlet content via Web services. JSR-168 and WSRP 1.0 portlet capabilities are tightly coupled. JSR-168 to WSRP portlet bridges utilize JSR-168's URL rewriting APIs. This article illustrates best practices for developing JSR-168 portlets for portability.
JSR 286 is a futuristic view of portlet specification 2.0 and the major working areas for JSR 286:
Coordination (Events support, Sharing session beyond portlet application, Sharing render parameters across portlets)
WSRP 2.0 alignment
Better support for Web Frameworks (JSF, Struts, Spring, WebWork)
AJAX Support
This aligns with J2EE 1.4, integrate other new JSRs relevant for the portlet, and align with the WSRP specification V 2.0
More : http://jcp.org/en/jsr/all
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment