@Target(value={TYPE,METHOD,FIELD}) @Retention(value=RUNTIME) @Documented @WebServiceFeatureAnnotation(id="http://www.w3.org/2005/08/addressing/module", bean=AddressingFeature.class) public @interface Addressing
This annotation MUST only be used in conjunction with the
WebService
, WebServiceProvider
,
and WebServiceRef
annotations.
When used with a javax.jws.WebService
annotation, this
annotation MUST only be used on the service endpoint implementation
class.
When used with a WebServiceRef
annotation, this annotation
MUST only be used when a proxy instance is created. The injected SEI
proxy, and endpoint MUST honor the values of the Addressing
annotation.
This annotation's behaviour is defined by the corresponding feature
AddressingFeature
.
Modifier and Type | Optional Element and Description |
---|---|
boolean |
enabled
Specifies if this feature is enabled or disabled.
|
boolean |
required
If addressing is enabled, this property determines whether the endpoint
requires WS-Addressing.
|
AddressingFeature.Responses |
responses
If addressing is enabled, this property determines whether endpoint
requires the use of anonymous responses, or non-anonymous responses,
or all.
|
public abstract boolean enabled
public abstract boolean required
public abstract AddressingFeature.Responses responses
AddressingFeature.Responses.ALL
supports all response types and this is the
default value.
AddressingFeature.Responses.ANONYMOUS
requires the use of only anonymous
responses. It will result into wsam:AnonymousResponses nested assertion
as specified in
3.1.2 AnonymousResponses Assertion in the generated WSDL.
AddressingFeature.Responses.NON_ANONYMOUS
requires the use of only non-anonymous
responses. It will result into
wsam:NonAnonymousResponses nested assertion as specified in
3.1.3 NonAnonymousResponses Assertion in the generated WSDL.
Submit a bug or feature
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.
Copyright © 1993, 2013, Oracle and/or its affiliates. All rights reserved.