JSR

JSR(Java Specification Request) “Write Content Once, Deliver It To Any Device!”

Approved Government Contractor

What is JSR?

Java Specification Request (JSR) the future of web programming languages is already going to have acceptance from all over the world. In simple words JSR is the actual description of proposed and final specifications for the Java platform. At any one time there are numerous JSRs moving through the review and approval process. JSR’s are reviewed by the JCP and the public before a final release of a specification is made.
The JSR projects found here are led by Specified leads who have decided to leverage java.net’s infrastructure for JSR development and collaboration. You will also find other JSR discussions that may or may not be led by Specifcations leads or those involved in the JSR development. Each java.net hosted JSR Project has a public area where discussions will take place between the community and those involved in the JSR development project.

“Write Content Once, Deliver It To Any Device!”

Need of JSR?

If you are writing web application which can be accessed from different devices (such as desktop browser, mobile devices), your application is required to deliver content according to the device capability. For example, your web page contains images but accessing devices is not supporting the rendering of images OR your web page contains too much data to be handled by the bandwidth of accessing device.

What is JSR 286? version 2.0

JSR (Java Specification Request) 286 is a proposed specification for version 2.0 of portlets. JSR’s are the part of Java Community Process (JCP) which is used to evolve Java platform with the help of community participation. The current portlet specification version is 1.0 which is also called JSR 168. The JSR 168 APIs are already in widely use and people are feeling some restrictions in the specification. The objective of the JSR 286 is to make the portlet API more matured incorporating all essential features. One can see this process as evolution of portlet API. Once the JSR 286 specifications are finished, portal vendors can implement these standard set of APIs to make portlets, based on JSR 286, interoperable among portals.

What is JSR 168?

Java Specification Request (JSR) 168 enables interoperability among portlets and portals. This specification defines a set of APIs for portlets and addresses standardization for preferences, user information, portlet requests and responses, deployment packaging, and security. Now, when portal developers and portal vendors adhere to this standard, any portlet developed for one portal server will be able to run on another portal server.

What is JSR 227?

In one sentence we say that JSR-227 defines a standard way for tools to implement the interactions between user interfaces and services, doing this in a way that will work for any user interface and any service technology. In the world of MVC applications the View and Controller layers need to interact with the Model layer. Until this JSR came along, the developer had to learn the specific API for the technology that implemented its Model layer in order to build his View and Controller layers. With JSR 227 there is a single standard API that works with any implementation of a Model layer – regardless of the implementing technology which can be EJB, SDO, XML, Javabeans, etc – as well as with any implementation of View layer, such as JSP, JSF, Struts, Swing or any new technology that might pop up.