• Post Reply Bookmark Topic Watch Topic
  • New Topic

What is new in 7?

 
Sitarama Swamy
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What is different or new in Java 7 WS at a high level?
 
Palak Mathur
Ranch Hand
Posts: 342
IntelliJ IDE Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sitarama Swamy wrote:What is different or new in Java 7 WS at a high level?


This question has already been asked few times in past few days. http://www.coderanch.com/t/585229/Web-Services/java/new-Java-JAX-WS
I am quoting Jeff from that post:-

Jean-Fran├žois Morin wrote:Hi Tina:

Basically, the version of JAX-WS included in Java SE 7 is the 2.2 specification. Some new features are listed on the following link: http://jax-ws.java.net/nonav/2.2.6-2/docs/ch02.html.

Here is an excerpt that features changed between versions 2.1.7 and 2.2:

  • Add WS-Addressing 1.0 Metadata support as per 2.2 spec
  • Support for @XmlElement on SEI's wrapper parameter
  • Support for @XmlType on exception classes
  • Implement HTTP SPI
  • mplement Endpoint API with features
  • Generate new constructors in the generated Service class(service level features, wsdllocation) *
  • Add support for customizing wrapper wsdl:part names as defined in 2.2
  • Add support for customizing wsdl:message name using @WebFault as defined in 2.2
  • Fault customization should accept fully qualified name of the exception class to be generated
  • Customization of Service should accept fully qualified class name
  • Add Xnocompile option for wsgen similar to wsimport
  • XPath expressions in jax-ws customization can now select multiple nodes
  • Disable server-side exception stacktrace for service specific exceptions
  • Optimzation of LogicalMessage implementation
  • wsimport now handles URL redirection of imported wsdls correctly


  • * I experienced myself this addition in the javax.xml.ws.Service class (extended by proxy generators created by wsimport). Unless your application classpath is configured in a very specific way, this may force you to stay with JAX-WS 2.0/2.1 if you are using Java SE 6, and go on with JAX-WS 2.2 if you use Java SE 7.


    Jeff


    http://jax-ws.java.net/nonav/2.2.6-2/docs/ch02.html.
     
    • Post Reply Bookmark Topic Watch Topic
    • New Topic
    Boost this thread!