Schema for JAX-WS 2.0 WSDL customization. TODO WSDL customization binding declaration. There are two ways to specify binding declarations. 1. All binding declarations pertainingto a given WSDL document are grouped together in a standalone document, called an external binding file. 2. The second approach consists in embeddeding binding declarations directly inside a WSDL document. In either case, the jaxws:bindings element is used as a container for JAX-WS binding declarations. It contains a (possibly empty) list of binding declarations, in any order. A binding declaration embedded in a WSDL document can only affect the WSDL element it extends. When a jaxws:bindings element is used as a WSDL extension, it MUST NOT have a node attribute. Moreover, it MUST NOT have an element whose qualified name is jaxws:bindings amongs its children. Location of the remote WSDL to associate binding declarations with. It MUST NOT be present if the jaxws:bindings element is used as an extension inside a WSDL document or one of its ancestor jaxws:bindings elements already contains this attribute. The value of the string is an XPATH 1.0 compliant string that resolves to a node in a remote WSDL to associate binding declarations with. The remote WSDL is specified by the wsdlLocation attribute occuring in the current element or in a parent of this element. The node attribute can be used to customize the inlined schema inside the WSDL, in this case the node attribute must point to the xs:schema node inside the WSDL. Further jaxb:bindings should be used as the child of jaxws:bindings. Example: NOTE: It MUST NOT be present if the jaxws:bindings appears inside a WSDL document. Used to indicate the version of WSDL customization declarations. Only valid on root level bindings element. If this is absent, it will implicitly be assumed to be 2.0. If absent, the default package name is computed from the targetNamespace of the WSDL in scope. The rules of targetNamespace to Java package name is described in the JAXB specification. Appears in the context of a WSDL document, either as an extension to the wsdl:definitions element or in an external binding file at a place where there is a WSDL document in scope. Scope: wsd;definitions Example: enableWrapperStyle can be used to disable wrapper style Java method generation. If absent the default value of enableWrapperStyle is true. Setting it to true may not result into wrapper style method generation unless the wrapper style rules are satisfied as defined in JAX-WS 2.1 specification 2.3.1.2. Scope: wsd;definitions, wsdl:portType, wsdl:portType/wsdl:operation. Example: false enableAsyncMapping can be used to enable async method generation in the entpoint interface generated from a WSDL. If absent the default value of enableAsyncMapping is false. See JAX-WS 2.1 spec section 2.3.4.2. Scope: wsd;definitions, wsdl:portType, wsdl:portType/wsdl:operation. Note: These generated async methods can be used only on the client side. Example: false If present the use of the mime:content information is enabled as defined in the JAX-WS 2.1 spec section 2.6.3.1 Scope: wsdl:definitions, wsdl:binding, wsdl:binding/wsdl:operation Example: false Customizes the name of generated classes for the SEI, service class or the fault class. Scope: wsd;portType - The name of generated SEI (Service Endpoint Interface) wsdl:portType/wsdl:operation/wsdl:fault - The generated fault class name. wsdl:service - Name of the generated Service class. Example: Customizes the name of Java method in the generated classes. Scope: wsd;portType/wsdl:operation - name of Java methods corresponding to wsdl:operation wsdl:service/wsdl:port - Name of the port getter in the generated Service class Example: Customizes the name of the Java method parameters in the generated SEI. Scope: wsd;portType/wsdl:operation wsdl:binding/wsdl:operation To rename wsdl:header (additional header parameters, this support is optional as JAX-WS 2.1 spec makes additional header mapping optional. Example: false A XPath expression identifying a wsdl:part child of a wsdl:message. The qualified name of a child element information item of the global type definition or global element declaration referred to by the wsdl:part identified by the previous attribute. It is optional and you need it only to rename parameters corresponding to wrapper style operation. The name of the Java formal parameter corresponding to the parameter identified by the previous two attributes. This binding declaration specifies that the annotated port will be used with the javax.xml.ws.Provider interface.