javax.xml.ws.soap
@Target(value=TYPE) @Retention(value=RUNTIME) @Documented @WebServiceFeatureAnnotation(id="http://www.w3.org/2005/08/addressing/module", bean=AddressingFeature.class) public @interface Addressing
This feature represents the use of WS-Addressing with either the SOAP 1.1/HTTP or SOAP 1.2/HTTP binding. Using this feature with any other binding is NOT required.
The following describes the effects of this feature with respect to be enabled or disabled:
The required
property can be used to
specify if WS-Addressing headers MUST
be present on incoming messages. By default the
required
property is false
.
The definition of this annotation is incomplete in this release of JAX-WS as
there is no standard way to convey the use of WS-Addressing via a WSDL and there is no
standard definition for the default value of WS-Addressing Action
headers;
however, the runtime behavior of this annotation is well-defined.
It is intended that a future version of
JAX-WS will require the use of the standard mechanism to convey the use
of WS-Addressing via WSDL and default values for WS-Addressing Action
headers
as defined by the W3C WG on WS-Addressing.
To write a portable endpoint and its corresponding client with this version of JAX-WS,
an endpoint MUST explicitly specify what WS-Addressing Actions
are to be used
via the Action
and FaultAction
annotations. The client MUST explicitly
enable addresssing via the AddressingFeature
, and for each invocation, the client
MUST explicitly set the BindingProvider.SOAPACTION_URI_PROPERTY
.
After the W3C WG on WS-Addressing has specified how the use of WS-Addressing is specified in the WSDL,
and what the default value must be for Action headers, a future version of JAX-WS will remove these requirements.
See Web Services Addressing - Core and Web Services Addressing 1.0 - SOAP Binding for more information on WS-Addressing.
Submit a bug or feature Copyright © 1993, 2017, Oracle and/or its affiliates. All rights reserved.
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.