Release Notes (original) (raw)

1. Required Software

• Requires JDK 6 or later
• Requires Ant 1.7.1 or later
• Tested with GlassFish v4.x and Apache Tomcat 5.5.20

2. Installation Instructions

The following applies to the JAX-WS standalone bundles.

• Extract JAX-WS RI 2.3.0-SNAPSHOT bundle
• To use with GlassFish
  • Glassfish contains JAX-WS within Metro package so no installation required. For updating JAX-WS installation in Glassfish please refer to Metro project.
• To install on Tomcat
  • Set CATALINA_HOME to your Tomcat installation.
  • Run
    ant install
    This essentially copies lib/*.jar from the root of JAX-WS RI extracted bundle to$CATALINA_HOME/shared/lib
  • If you are running on top of JDK6, run
    ant install-api
    or use
    ant -help
    for detailed information.

If you intend to only invoke an already existing Web service, then alternatively you can use the wsimport andwsgen scripts in the bin directory of the JAX-WS RI 2.3.0-SNAPSHOT bundle.

3. Running on top of JDK 6

JDK includes JAX-WS and JAXB API and RI. JAX-WS RI 2.3.0-SNAPSHOT includes RI of JAX-WS/JAXB 2.2. In order to run JAX-WS RI 2.3.0-SNAPSHOT you would need to specify ONLYjaxws-api.jar, andjaxb-api.jar jars using the Java Endorsed Standards Override Mechanism

4. Jar dependency

Table 1. Jar dependencies summary

If you run JAX-WS RI 2.3.0-SNAPSHOT with IBM JDK, there are two options:

• to add Oracles's JAXP implementation jars along
• to remove the saaj-impl.jar from the libraries in order IBM SAAJ implementation to be used

JAXWS also depends on resolver implementation form JDK, which is not found on AIX. The repackaged resolver.jar can be found in the distribution, or Maven though. First approach is recommended.

5. Current Limitations / Bugs / Issues

• The java.util.Collection classes cannot be used with rpc/literal or document/literalBARE style due to a limitation in JAXB. However, they do work in the default document/literalWRAPPED style.
• Although JAX-WS customizations are portable across implementations, the names of WSDL and schema files generated are not specified. Therefore each vendor may and most likely will generate different names. Therefore, when switching between implementations of JAX-WS, it may be necessary to modify your customization files to reflect different WSDL and schema file names.
• This holds true for different releases of the JAX-WS RI. The JAX-WS RI may in each release change these file names to resolve bugs. If and when this does occur, a developer would need to change the filenames in their customization files to match the new file names.

6. Changelog

• 2.2.8
  ** Bug

  • [JAX_WS-692] - WsImport fails if wsdl:message/wsdl:part defines "type" (not "element")

  • [JAX_WS-713] - Document MTOM limitations

  • [JAX_WS-1062] - wsimport command will throw NullPointerException when no difination of like "xmlns:undns="http://test"" in WSDL file.

  • [JAX_WS-1064] - Need to use Filer when generating files

  • [JAX_WS-1068] - Issue with two or more web services in the same war when pointing to wsdls in different META-INF/wsdl subdirs where the wsdl files themselves are the same.

  • [JAX_WS-1074] - ClassCast exception when wsimport task run in a forked mode

  • [JAX_WS-1083] - Error listenerStart Sep 27, 2012 12:02:48 AM org.apache.catalina.core.StandardContext start

  • [JAX_WS-1087] - unable to delete .war file after wsimport completed

  • [JAX_WS-1092] - Back Compatible issue, for method: com.sun.xml.ws.server.EndpointFactory.verifyImplementorClass

  • [JAX_WS-1095] - Basic Authentication with wsimport does not allow @ in username

  • [JAX_WS-1098] - IllegalAnnotationsException: 2 counts of IllegalAnnotationExceptions: MemberSubmissionEndpointReference$Address and W3CEndpointReference$Address

  • [JAX_WS-1099] - com.sun.xml.ws.api.model.wsdl.WSDLModel.WSDLParser.parse error in parsering wsdl:message/wsdl:part defines "type" (not "element")

  • [JAX_WS-1101] - wsimport authFile URL containing passwords should support encoded/escaped characters...

  • [JAX_WS-1105] - wsgen fails to resolve all 'service implementation bean' methods

  • [JAX_WS-1107] - httpproxy username and password not supported

  • [JAX_WS-1118] - Broken links in the guide
    ** Improvement

  • [JAX_WS-143] - wsimport does not support jaxb plugins

  • [JAX_WS-261] - Make WSServletDelegate class public

  • [JAX_WS-1100] - Allow wild card matching to allow the same user:password for all urls with the same host name

  • [JAX_WS-1102] - jaxws should pass encoding option to jaxb

  • [JAX_WS-1112] - Make JAX-WS run on J2SE 5.0 - fixed documentation to not refer to JDK5
    ** Task

  • [JAX_WS-1042] - The documentation in http://jax-ws.java.net/2.2.5/docs/wsgenant.html is incorrect

  • [JAX_WS-1080] - move build from ant to maven

  • [JAX_WS-1082] - consider updating dependencies

  • See Section 18, “External Web Service Metadata” for more information on External metadata support.

  • JAXB version updated to 2.2.7, for changes see JAXB Changelog

• 2.2.7 - 2.2.3 - TBD to be added
• 2.2.3
  • Add -clientjar option for wsimport
  • Add support for Async Servlet Transport using Servlet 3.0 api
  • Bug fixes
• 2.2.1
  • wsgen can inline schemas in a generated wsdl using a switch
  • Schema Validation support is enhanced
  • Bug fixes
• 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
  • Implement 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
  • Bug fixes
• 2.1.7
  • Bug fixes
• 2.1.6
  • Supportfor transport attribute for bindings like SOAP/JMS binding
  • Bug fixes
• 2.1.5
  • Allowing HTTP response code to be set via MessageContext property
  • New feature: UsesJAXBContextFeature, to control JAXBContext creation
  • Newwsimport option: -XdisableSSLHostnameVerfication, to disable SSL Hostname verification
  • Wsimport ant task accepts nested args for specifying additional options
  • Bug fixes
• 2.1.4
  • Simplified "Starting from Java Programming model" through dynamic generation of request and response wrappers
  • Support for dual binding (SOAP/HTTP and XML/HTTP) for the same service class
  • Bug fixes
• 2.1.3
  • Authentication support in wsimport
  • Additional header support
  • Large and Streaming attachment support
  • XML Schema validation support for SOAP message
  • Expose the -Xnocompile as an Ant task option
  • Additional WSDL object methods for policy
  • Wsimport should be able to handle redirects and see Others
  • Remove SJSXP and SAAJ RI dependency
  • Wsimport should write to passed OutputStream
  • Efficient Handler using Handler support
  • Bug fixes
• 2.1.2
  • JMX Agent for the server side
  • Mtom Interop with .NET 2.0/WSE 3.0
  • Bug fixes
• 2.1.1
  • JAXB 2.1 RI Integration
  • JAX-WS 2.1 MR (JSR 224) implementation
  • Type substitution support
  • WS-Addressing - W3C and Memeber Submission
  • APIs to create EPR and use it to invoke endpoint
  • Support for enabling/disabling features, such as WS-Addressing/MTOM
  • Asynchronous server
  • Tubes and Fiber for asynchronous message processing
  • Dispatch and Provider
  • Stateful Webservice support
  • Bug fixes