Introduction to JSR-227
About author I am Oracle/Java professional.Working on J2EE technologies and i.e Oracle ADF,Java,J2ee,PL/sql,Top Link,Apps for 2+ years.I am passionate about learning new technologies.I am sharing my knowledge. Give your views and suggestion.
http://www.linkedin.com/in/vinaykumar2 Read more from this authorJSR-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. MVC is application design pattern in this.Primary supported by Sun+oracle. JSR 227 defines an
abstraction mechanism. We are accessing data from JavaBeans, EJB, JDO or POJO in order to reterive our view. 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. This will be beneficial for two group one is Developer who design UI interface. The other group is providers of business services. For example I might be a business service provider with an innovative way to implement business service. Now all I need to do is provide a data control implementation to my business service – any tool that supports JSR-227 will be able to use my business services in a transparent way.
JSR-227 influence the future of application development :-
JSR-227 as an enabling standard for Service Oriented Architecture (SOA). The concept of SOA is that you can pick up services from anywhere and use them in your application. What JSR-227 will enable you to do is ignore the specific implementation of the service and easily bind user interfaces to this service. This helps create the needed separation between service developers and application developers.
More information you can find on :-
1.www.oracle.com
2. http://web1.jcp.org/en/jsr/detail?id=227(JSR 227 home page)
References
http://www.oracle.com/technology/tech/java/newsletter/articles/jsr227_interview.html
Comments
I wish there was more interest in JSR -227 from folks other than at Oracle.
I see JSR-227 being critical as a business-case enabler, not just a technical enabler. After all, WebMethods and JBoss already do a good job at gluing together the disparate technologies.
I think for “cloud” services to take off and be accepted by clients, appart from changing the name from “cloud” to something less ephemeral, standards like JSR-227 need to be adopted broadly by service integrators and providers. Otherwise how, as a customer, do I avoid the next wave of consumer lock-in?
I would think HP, IBM, Microsoft and Sun/Oracle can all partner to make “the cloud” more attractive by focussing on work such as this, and I’ll be pushing from the inside where I can.
Trackbacks