[image]
[image] [image]
[image]
[image]
[image][image][image][image][image][image][image][image][image] [image] [image] 635522 members! Sign up to stay informed. [image] [image] [image] [image]
[image]

Sponsored Links


Resources

Enterprise Java
Research Library

Get Java white papers, product information, case studies and webcasts

[image]Blogs Blogs Blogs Messages: 1 Messages: 1 Messages: 1 [image]Printer friendly Printer friendly Printer friendly [image]Post reply Post reply Post reply [image]XML XML XML [image]
[image]

Simplifying Web Service development with JSR-181

Posted by: Daniel Rubio on Sun Mar 02 15:36:19 EST 2008 DIGG
JSR-181 provides the foundations to develop Java Web Services with the same techniques used by Spring and other lightweight frameworks, namely those of using Plain Old Java Objects (POJO's) and annotations. This article provides numerous examples on using this technique


JSR 181 or Web Services Metadata for the Java Platform is a Java Specification Request that defines an annotated Java format that uses Java Language Metadata (JSR 175) to enable easy definition of Java Web Services in a J2EE container. To put simply, JSR 181 enables developers to create portable Java Web Services from a simple Plain Old Java Object (POJO) class by adding annotations.

This Web Service development model may be related to JSP model where a JSP file is translated into a Servlet that gets in turn compiled to a class file that finally runs inside the container. The JSP model frees the developers from manual compilation and deployment of Servlets into container. Similarly in this model too, Web Service developers defines only the annotated Java Web Service (JWS) file and leave the job of creating necessary deployment and configuration files to the vendor (who actually implements Web Services based on JSR 921 specification). For example, WebLogic application server provides an Ant task called jwsc to create the JSR 921 compliant Web Service implementations. As the generation of JSR 921 compliant Web Services is hidden to developers, they can focus on developing core business services rather than worrying on learning and implementing generalized APIs and deployment descriptors.

The annotated Web Service development model also provides fine-grained control over exposing the Web Services. It enables the developers to expose the entire class or only the selected methods as the Web Service. This feature may be of great help when the Java class contains core business methods bundled along with non-business methods and/or data service methods, which the developer might not want to expose as services. In this scenario, the developer may take advantage of the annotations to specify how a Web Service should be exposed to outside world.

Putting simply, JSR 181 is a specification to define standard and portable Web Services. It offers the following benefits:

* Provide a simplified model for developing Web Services
* Abstract the implementation details
* Achieve robustness, easy maintenance, and high interoperability


Read the entire post on Simplfying Web Service with JSR-181:
http://www.developer.com/java/ent/article.php/3730756
[image]  Message #248409 [image]Post reply Post reply Post reply [image]Go to top Go to top Go to top [image]
[image]

You mean JSR-181

Posted by: Frank Martinez on Tue Mar 04 15:20:26 EST 2008 in response to Message #248286
You mean JSR-181 "Web Services Metadata for the Java Platform"
JSR-118 Is "Mobile Information Device Profile 2.0"

[image]
[image]Featured SectionFeatured SectionFeatured Section [image]
[image]
[image]Weekly Blogs UpdateWeekly Blogs UpdateWeekly Blogs Update [image]
[image]
Stay current on the most informative blogs in the enterprise Java community. Join TheServerSide.com and sign up for the Blogs Update. Let TheServerSide.com do the work for you -- we scan thousands of blogs to find the ones most worthy of your attention.
[image]Featured BlogsFeatured BlogsFeatured Blogs [image]
[image]

Optimizing CMP Performance in Weblogic with Long-term Caching

[image] Dmitri Maximovich has written a blog on optimizing CMP EJB performance in WebLogic, by addressing optimistic concurrency, along with some of the implications of doing so.

Using Lucene with OJB

[image] Brian McCallister looks at the Lucene search engine and shows us how to index and retrieve objects from a sample Student application.

JDK 5 in Practice

[image] Cedric Beust has been in a position to actually code with JDK 5 for over six months. He has written up his thoughts on the new features, and how he has found them to be in practice.

Dear Manager, They Need a Build Machine

[image] Mike Clark has started a series of entries of letters that you wish you could write to your boss. It consists of concepts which seem so obvious to us, but which the bosses don't get.

Are we doing OR mapping wrong?

[image] Brian McCallister has been playing with JDO 2 fetch groups, ZODB, thinking about TranQL, playing with Prevayler, and looking at TORPEDO.

Fear and Testing

[image] Frank talks about fear and how it can derail efforts to find and solve scalability and performance problems. He has seen a lot of fear on his various engagements, and here he talks about why, and how.

Components, Design, and Functions

[image] Brian McCallister has kindly rambled on about IoC, and design in web applications. He discusses what has worked well for him (and others) in the last year.

JDK 1.5 from Joshua and Neal

[image] Matt Raible went to the Denver JUG meeting with Neal Gafter, and Joshua Bloch. They discussed the new features of Java 5, and Matt details the features, and when to use them.

News | Blogs | Discussions | Tech talks | Patterns | Reviews | White Papers | Downloads | Articles | Media kit | About
All Content Copyright ©2007 TheServerSide Privacy Policy
Site Map


You are viewing a mobilized version of this site...
View original page here

Mobilized by Mowser Mowser