Skip to main content
Release Notes
Release Notes
Prev   Next
Links: Table of Contents | Single HTML | Single PDF

Release Notes

Table of Contents

1. Required Software
2. Installation Instructions
3. Jar dependency
4. Current Limitations / Bugs / Issues
5. Changelog

1. Required Software

  • Requires Java SE 11 or later

  • Requires Ant 1.10.6 or later

  • Tested with GlassFish v7.x and Apache Tomcat 10.1.x

2. Installation Instructions

The following applies to the Eclipse Implementation of XML Web Services standalone bundles.

  • Extract Eclipse Implementation of XML Web Services 4.0.0 bundle

  • To use with GlassFish

    • GlassFish contains Eclipse Implementation of XML Web Services within Metro package so no installation required. For updating Eclipse Implementation of XML Web Services 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 Eclipse Implementation of XML Web Services extracted bundle to $CATALINA_HOME/shared/lib and updates shared.loader property in $CATALINA_HOME/conf/catalina.properties file.

If you intend to only invoke an already existing Web service, then alternatively you can use the wsimport and wsgen scripts in the bin directory of the Eclipse Implementation of XML Web Services 4.0.0 bundle.

3. Jar dependency

Table 1. Jar dependencies summary

Use

Description

Jar

Runtime

Jars required to run Web Services

angus-activation.jar, angus-mail.jar

FastInfoset.jar, gmbal-api-only.jar

ha-api.jar, jakarta.activation-api.jar

jakarta.annotation-api.jar, jakarta.mail-api.jar

jakarta.xml.bind-api.jar, jakarta.xml.soap-api.jar

jakarta.xml.ws-api.jar, jaxb-core.jar

jaxb-impl.jar, jaxws-rt.jar

management-api.jar, mimepull.jar

saaj-impl.jar, stax2-api.jar

stax-ex.jar, streambuffer.jar

woodstox-core.jar

Tools

Jars required to develop Web Services

jaxb-jxc.jar, jaxb-xjc.jar

jaxws-tools.jar

+ all the runtime jars


Table 2. JPMS module names

Jar

Module name

Maven GAV

angus-activation.jar

com.sun.activation.registries

org.eclipse.angus:angus-activation

angus-mail.jar

com.sun.mail

org.eclipse.angus:angus-mail

FastInfoset.jar

com.sun.xml.fastinfoset

com.sun.xml.fastinfoset:FastInfoset

gmbal-api-only.jar

gmbal

org.glassfish.gmbal:gmbal-api-only

ha-api.jar

org.glassfish.ha.api

org.glassfish.ha:ha-api

jakarta.activation-api.jar

jakarta.activation

jakarta.activation:jakarta.activation-api

jakarta.annotation-api.jar

jakarta.annotation

jakarta.annotation:jakarta.annotation-api

jakarta.mail-api.jar

jakarta.mail

jakarta.mail:jakarta.mail-api

jakarta.xml.bind-api.jar

jakarta.xml.bind

jakarta.xml.bind:jakarta.xml.bind-api

jakarta.xml.soap-api.jar

jakarta.xml.soap

jakarta.xml.soap:jakarta.xml.soap-api

jakarta.xml.ws-api.jar

jakarta.xml.ws

jakarta.xml.ws:jakarta.xml.ws-api

jaxb-core.jar

com.sun.xml.bind.core

com.sun.xml.bind:jaxb-core

jaxb-impl.jar

com.sun.xml.bind

com.sun.xml.bind:jaxb-impl

jaxb-jxc.jar

com.sun.tools.jxc

com.sun.xml.bind:jaxb-jxc

jaxb-xjc.jar

com.sun.tools.xjc

com.sun.xml.bind:jaxb-xjc

jaxws-rt.jar

com.sun.xml.ws

com.sun.xml.ws:jaxws-rt

jaxws-tools.jar

com.sun.tools.ws

com.sun.xml.ws:jaxws-tools

management-api.jar

org.glassfish.external.management.api

org.glassfish.external:management-api

mimepull.jar

org.jvnet.mimepull

org.jvnet.mimepull:mimepull

saaj-impl.jar

com.sun.xml.messaging.saaj

com.sun.xml.messaging.saaj:saaj-impl

stax2-api.jar

org.codehaus.stax2

org.codehaus.woodstox:stax2-api

stax-ex.jar

org.jvnet.staxex

org.jvnet.staxex:stax-ex

streambuffer.jar

com.sun.xml.streambuffer

com.sun.xml.stream.buffer:streambuffer

woodstox-core.jar

com.ctc.wstx

com.fasterxml.woodstox:woodstox-core


4. Current Limitations / Bugs / Issues

  • The java.util.Collection classes cannot be used with rpc/literal or document/literal BARE style due to a limitation in Jakarta XML Binding. However, they do work in the default document/literal WRAPPED style.

  • Although Jakarta XML Web Services 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 Jakarta XML Web Services, 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 Eclipse Implementation of XML Web Services. The Eclipse Implementation of XML Web Services 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.

  • Running a web service on Java SE Lightweight HTTP Server on Linux requires setting -Dsun.net.httpserver.nodelay=true to avoid delays in response. See #594 for more details.

5. Changelog

  • 4.0.0 - initial release for Jakarta EE 10

    • Requires Java SE 11 or newer

    • Supports usage of JAXWS 2.x WSDL bindings customizations

    • Uses XML-WS and XML-B acronyms instead of JAXWS/JAXB

    • wsimport: drop support for -target 2.0, 2.1 and 2.2

    • #98: Memory leak on ThreadLocalContainerResolver

    • #250: Spell dumpThreshold correctly, keeping misspelled legacy option dumpTreshold as a fallback

    • #336: wsimport: -target option does not generate old javax.xml.ws package name

    • #542: HttpTransportPipe.dump=true freeze with binary messages

    • #562: JAXBWrapperAccessor fails to find getters/setters

    • #582: Use 'Content-ID: ' header instead of ' Content-Id:'

    • #597: impossible cast in spi/db/TypeInfo

  • 3.0.2

    • #73: Serialization error when using SOAPHandler and Eclipselink plugin JAXBContextFactory

    • #215: WsImport.doMain() not closing binding file upon subsequent invocations

    • #221: Validate Custom Variable Name in Tester Servlet

  • 3.0.1

    • wsgen: added ability generate WSDL/Schema files only

    • wsgen: avoid NPE when reporting errors

    • wsgen: fixed fork=true invocation

    • mvn plugin: add Eclipse m2e lifecycle mapping

    • mvn plugin: allow definition of more seis in one plugin execution

    • wsimport: generate javax when target < 3.0

    • wsimport: mark-generated sometimes produces a wrong date value

  • 3.0.0 - initial release for Jakarta EE 9

    • Requires Java SE 8 or newer

    • Adopts new API package namespaces - jakarta.jws.* and jakarta.xml.ws.*

    • Supports new namespace for WSDL customizations 

      <bindings xmlns="https://jakarta.ee/xml/ns/jaxws version="3.0">...</bindings>

    • Supports new namespace for handler configuration files 

      <jws:handler-config xmlns:jws="https://jakarta.ee/xml/ns/jakartaee">...</jws:handler-config>

  • 2.3.2 - initial release for Jakarta EE 8

    • First release under Eclipse Jakarta EE Platform

    • Uptake of moved Jakarta APIs.

Prev   Next
Overview Home Users Guide

Back to the top