• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

JSR168 vs JSR 286

Ranch Hand
Posts: 608
Eclipse IDE Spring Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

How big are the differences between the portlet V1 and V2 specs??You see unfortunately I bought a JSR168 book that was quite expensive when it turns out we are going to be using 286 from now on...

I'm hoping that studying the 168 book will still give me most of the info I need to develop the 286 portlets...
Ranch Hand
Posts: 197
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi duran,

check this,

JSR-168 – What is missing?
• inter-portlet communication
• serving non-html resources (pdf, doc, images etc.)
• contributing javascript or css to <head>, using cookies
• proper support for common web frameworks
• portlet filters
Inter-portlet communication
• only supported within the same portlet application
using session attributes
• target portlets will only “see” messages during next
render request
• portlets cannot (should not) update their state during a
render request: “event” handling not really possible
Serving non-html resources
• A portlet can only render html fragments
• Have to fallback/delegate to the servlet container
• Requires coordination between portlet and servlet
Contributing to <head>, setting cookies
• javascript or css can only be embedded withing the
content markup; no body onLoad handling hooks
• API forbids adding cookies: only client side setting of
cookies using javascript is possible
Proper support for common web frameworks
• Most web frameworks are Servlet API only
• Servlet dispatching not supported from processAction
• Needs Portals Bridges or similar solutions
• JSTL support very limited:
<c:out value=”<%= ((FooBean)renderRequest.getSession()
.getBeanValue() %>"/>

JSR-286 - Coming up

• Portlet Specification 2.0
• Expert Group started January 2006
• 1st Early Public Draft released August 2006
covering most, but not yet all, planned features
• 2nd Early Public Draft November 2006
covering all features
• 1st Public Draft December 2006
• Final Release May 2007
• RI will be done under Apache Pluto umbrella with help
from a group at University of Jena
• Binary compatible with JSR-168
• Alignment with J2EE 1.4, WSRP 2.0
• Portlet coordination
• Public render parameters
• Shared session state across applications (maybe)
• Portlet events
• Resource serving
• AJAX support
• Portlet filters
• Extended cache support
• Improved support for common web frameworks
• ... and more ...

To do a great right, do a little wrong - shakepeare. twisted little ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic