Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Specifications?

 
Veeramanikandan Radhakrishnan
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hai,

i just got confused over the specifications like JSR 168 and others...

someone help out...

What is the need and the difference between the specifications?

also what are all the specifications available?

 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think most technologies go through a standardization process, getting requests from vendors and the linke. For Portlets, the JSR that represented the agreement on the first, standard portlet API, was JSR 168. The next one will be JSR-268.

There are all sorts of JSR's out there. Just head over to sun's Java website and search for them.

Here's a link to the JSR-168 Portlet Specification, where you can download both the JSR168 specification, and the Portlet JavaDoc as well.

This is the Final Release of this Specification, as described in Section 3.4 of the Java Community ProcessSM Program, version 2.1.

If you really want to be forward thinking when it comes to portlet development, take a look at the JSR-286 Portlet Specification from Sun (as opposed to the JSR-268 specification):

JSR 286: Portlet Specification 2.0

You can even get a real intimidating list of all the JSR requests right here:

All of the JSRs Sun is Working On

-Cameron McKenzie

[ March 03, 2007: Message edited by: Cameron W. McKenzie ]
[ March 03, 2007: Message edited by: Cameron W. McKenzie ]
 
Shailesh Joshi
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Veeramanikandan,
Cameron is right...JSR is nothing but a standardized behavior of any functionality a vendor should provide. so being JSR 168 compliant, Sun ONE Server, IBM WPS 5.1.x, JetSpeed 2.x etc should present same behavior of your portal application when deployed on any of them. Internal mechanism may be different and abstract to portal developers.

when it doesn't behave according to JSR, well we get patches and fixes

Hope this is helpful.

cheers
Shailesh
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic