- java.lang.Object
-
- javax.xml.ws.WebServiceFeature
-
- javax.xml.ws.RespectBindingFeature
-
public final class RespectBindingFeature extends WebServiceFeature
This feature clarifies the use of thewsdl:binding
in a JAX-WS runtime. This feature can be used during the creation of SEI proxy, andDispatch
instances on the client side andEndpoint
instances on the server side. This feature cannot be used forService
instance creation on the client side.This feature is only useful with web services that have an associated WSDL. Enabling this feature requires that a JAX-WS implementation inspect the
wsdl:binding
for an endpoint at runtime to make sure that allwsdl:extensions
that have therequired
attribute set totrue
are understood and are being used.The following describes the affects of this feature with respect to be enabled or disabled:
- ENABLED: In this Mode, a JAX-WS runtime MUST assure that all
required
wsdl:binding
extensions(including policies) are either understood and used by the runtime, or explicitly disabled by the web service application. A web service can disable a particular extension if there is a correspondingWebServiceFeature
or annotation. Similarly, a web service client can disable particular extension using the correspondingWebServiceFeature
while creating a proxy or Dispatch instance. The runtime MUST also make sure that binding of SEI parameters/return values respect thewsdl:binding
. With this feature enabled, if a required (wsdl:required="true"
)wsdl:binding
extension is in the WSDL and it is not supported by a JAX-WS runtime and it has not been explicitly turned off by the web service developer, then that JAX-WS runtime MUST behave appropriately based on whether it is on the client or server:- Client: runtime MUST throw a
WebServiceException
no sooner than when one of the methods above is invoked but no later than the first invocation of an endpoint operation. - Server: throw a
WebServiceException
and the endpoint MUST fail to deploy
- Client: runtime MUST throw a
- DISABLED: In this Mode, an implementation may choose whether
to inspect the
wsdl:binding
or not and to what degree thewsdl:binding
will be inspected. For example, one implementation may choose to behave as if this feature is enabled, another implementation may only choose to verify the SEI's parameter/return type bindings.
- Since:
- JAX-WS 2.1
- See Also:
AddressingFeature
- ENABLED: In this Mode, a JAX-WS runtime MUST assure that all
required
-
-
Field Summary
Fields Modifier and Type Field and Description static String
ID
Constant value identifying the RespectBindingFeature-
Fields inherited from class javax.xml.ws.WebServiceFeature
enabled
-
-
Constructor Summary
Constructors Constructor and Description RespectBindingFeature()
Creates anRespectBindingFeature
.RespectBindingFeature(boolean enabled)
Creates an RespectBindingFeature
-
-
-
Field Detail
-
ID
public static final String ID
Constant value identifying the RespectBindingFeature- See Also:
- Constant Field Values
-
-
Constructor Detail
-
RespectBindingFeature
public RespectBindingFeature()
Creates anRespectBindingFeature
. The instance created will be enabled.
-
RespectBindingFeature
public RespectBindingFeature(boolean enabled)
Creates an RespectBindingFeature- Parameters:
enabled
- specifies whether this feature should be enabled or not.
-
-
Method Detail
-
getID
public String getID()
Get the unique identifier for this WebServiceFeature.- Specified by:
getID
in classWebServiceFeature
- Returns:
- the unique identifier for this feature.
-
-
Document created the 11/06/2005, last modified the 04/03/2020
Source of the printed document:https://www.gaudry.be/en/java-api-rf-javax/xml/ws/RespectBindingFeature.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.