This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Five Lines of Code and have Christian Clausen on-line!
See this thread for details.
Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!
  • 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 ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Mark Hansen - JWS, JEE 6

 
Ranch Hand
Posts: 148
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I know that the JEE 6 jsr has been recently sumitted and withdrawn, but looking at it briefly it seemed represent a minimal change in the JEE specification from JEE 5.

Do you know if there are any SOA - Web Services changes proposed for JEE 6.

Furthermore may I ask you if all the changes from JAX-RPC to JWS represent only syntatic sugar???
 
author
Posts: 61
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Java EE 6 will include at least one major Web Services enhancement: JSR-311 - The Java API for RESTful Web Services. The intent is to make RESTful endpoint development and deployment much easier than it is with JAX-WS or plain servlets.

The change from JAX-RPC to JAX-WS is fundamental, and represents much more than just syntactic sugar. The following comes from Chapter 1 of my book:

"As one example of how the JWS [Java Web Services] specifications have improved, consider JAX-WS 2.0. Chapters 6 and 7 describe that specification in detail, so for now, I'm just going to give a preview of why I think it's such a big improvement over JAX-RPC 1.1. For starters, the JAX-RPC data binding has been removed and the specification has been simplified to focus on the WSDL to Java mapping along with support for REST endpoints. The XML Schema to Java data binding from JAX-RPC has been replaced with JAXB 2.0, a much superior and widely used technology. Second, JAX-WS lets you use annotations to control the shape of the WSDL generated from a Java interface. The use of annotations in this manner simplifies and in some cases eliminates the need for the deployment descriptors required to deploy a JAX-RPC service. Third, JAX-WS provides interfaces (Dispatch on the client side, and Provider on the server side) that enable programmers to directly access and work with XML � effectively bypassing the JAXB data binding when they don't want to use it."
 
I carry this gun in case a vending machine doesn't give me my fritos. This gun and this tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic