The Hebrew University Magnes Press


 View book pages:
  




BETTER SUPPORT OF EXISTING

by Joey Bernal, Peter Blinstrubas, Tim Hanis, Stefan Hepper, Ron Lynn, Cayce Marston, Usmon Memon, Varadarajan Ramamoorthy
BETTER SUPPORT OF EXISTING WEB FRAMEWORKS More and more Web frameworks now support portlets beside servlets as a programming model. Examples of such Web frameworks include JavaServer Faces ( JSF), Spring, Struts, and WebWork. Most of these frameworks started before portlets were born and thus have strong ties into the servlet programming model. To make the adoption of portlets as the controller part in the Model- View- Controller ( MVC) pattern easier in these frameworks, JSR 286 introduces the ability to dispatch to servlets and JSPs in all life- cycle methods ( e. g., for implementing controller logic in a servlet) and supports portlet filters for presetting values in the request or wrapping objects in the portlet request. ( For information about the MVC pattern, see Chapter 4.) CLIENT- CAPABILITIES ACCESS Access to client capabilities gives the portlet the ability to take special client capabilities, such as screen size, into account when generating the markup. For client capabilities, the Composite Capabilities/ Preferences Profiles ( CC/ PP) standard from W3C allows defining device capabilities, and the User Agent Profile ( UAProf) provides specific attributes definitions for individual devices. The CC/ PP standard is now available as a Java API specified in JSR 188 ( for information about the JSR 188 specification, see http:// jcp. org/ en/ jsr/ detail? id= 188). However, because JSR 188 was developed in parallel with the portlet specification, it doesn’t take portlets into account, and the factory in CC/ PP that lets you get the profile of a client takes only HttpServletRequest, not PortletRequest, as an input parameter. Therefore, either the CC/ PP API needs to be extended to also take a PortletRequest as an input parameter or the portlet specification needs to add a method that directly returns a CC/ PP client profile. ADVANCED CACHING At present, the caching options for portlets are restricted to expiration- based caching. However, this is a very static approach that is too coarse- grained for many applications. Advanced caching capabilities would enable the portlet to provide caching information that goes beyond this simple expiration mechanism of the first version. APPENDIX A: Looking Toward V2.0 of the Java Portlet Specification 470

Zoom in  zoom  Zoom out
  << Topic >>  | Contents | Index             |<   <<    Page       >>   >|  
BETTER SUPPORT OF EXISTING WEB FRAMEWORKS More and more Web frameworks now support portlets beside servlets as a programming model. Examples of such Web frameworks include JavaServer Faces ( JSF), Spring, Struts, and WebWork. Most of these frameworks started before portlets were born and thus have strong ties into the servlet programming model. To make the adoption of portlets as the controller part in the Model- View- Controller ( MVC) pattern easier in these frameworks, JSR 286 introduces the ability to dispatch to servlets and JSPs in all life- cycle methods ( e. g., for implementing controller logic in a servlet) and supports portlet filters for presetting values in the request or wrapping objects in the portlet request. ( For information about the MVC pattern, see Chapter 4.) CLIENT- CAPABILITIES ACCESS Access to client capabilities gives the portlet the ability to take special client capabilities, such as screen size, into account when generating the markup. For client capabilities, the Composite Capabilities/ Preferences Profiles ( CC/ PP) standard from W3C allows defining device capabilities, and the User Agent Profile ( UAProf) provides specific attributes definitions for individual devices. The CC/ PP standard is now available as a Java API specified in JSR 188 ( for information about the JSR 188 specification, see http:// jcp. org/ en/ jsr/ detail? id= 188). However, because JSR 188 was developed in parallel with the portlet specification, it doesn’t take portlets into account, and the factory in CC/ PP that lets you get the profile of a client takes only HttpServletRequest, not PortletRequest, as an input parameter. Therefore, either the CC/ PP API needs to be extended to also take a PortletRequest as an input parameter or the portlet specification needs to add a method that directly returns a CC/ PP client profile. ADVANCED CACHING At present, the caching options for portlets are restricted to expiration- based caching. However, this is a very static approach that is too coarse- grained for many applications. Advanced caching capabilities would enable the portlet to provide caching information that goes beyond this simple expiration mechanism of the first version. APPENDIX A: Looking Toward V2.0 of the Java Portlet Specification 470
Zoom in  zoom  Zoom out
  << Topic >>  | Contents | Index             |<   <<    Page       >>   >|  

MC Press Online - 978-1-931182-28-7


 Other related titles:
IBM WebSphere Portal PrimerIBM WebSphere Portal Primer
SOA for the Business DeveloperSOA for the Business Developer
You Want to Do What with PHP?You Want to Do What with PHP?

 Already viewed books:
Programming PortletsProgramming Portlets