Add support for <addressing> <respect-binding> & <mtom-threshold> subelements of <port-component-ref> element -------------------------------------------------------------------------------------------------------------- Key: JBMETA-299 URL: https://jira.jboss.org/browse/JBMETA-299 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Components: common Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jboss-metadata-common-2.0.0-alpha-17 <xsd:complexType name="port-component-refType"> <xsd:annotation> <xsd:documentation> The port-component-ref element declares a client dependency on the container for resolving a Service Endpoint Interface to a WSDL port. It optionally associates the Service Endpoint Interface with a particular port-component. This is only used by the container for a Service.getPort(Class) method call. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:element name="service-endpoint-interface" type="javaee:fully-qualified-classType"> <xsd:annotation> <xsd:documentation> The service-endpoint-interface element defines a fully qualified Java class that represents the Service Endpoint Interface of a WSDL port. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="enable-mtom" type="javaee:true-falseType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation> Used to enable or disable SOAP MTOM/XOP mechanism on the client side for a port-component. Not to be specified for JAX-RPC runtime </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="mtom-threshold" type="javaee:xsdNonNegativeIntegerType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation> When MTOM is enabled, binary data above this size in bytes should be XOP encoded or sent as attachment. Default value is 0. Not to be specified for JAX-RPC runtime </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="addressing" type="javaee:addressingType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation> This specifies the WS-Addressing requirements for a JAX-WS web service. It corresponds to javax.xml.ws.soap.Addressing annotation or its feature javax.xml.ws.soap.AddressingFeature. See the addressingType for more information. Not to be specified for JAX-RPC runtime </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="respect-binding" type="javaee:respect-bindingType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation> Corresponds to the javax.xml.ws.RespectBinding annotation or its corresponding javax.xml.ws.RespectBindingFeature web service feature. This is used to control whether a JAX-WS implementation must respect/honor the contents of the wsdl:binding in the WSDL that is associated with the service. Not to be specified for JAX-RPC runtime </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="port-component-link" type="javaee:string" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation> The port-component-link element links a port-component-ref to a specific port-component required to be made available by a service reference. The value of a port-component-link must be the port-component-name of a port-component in the same module or another module in the same application unit. The syntax for specification follows the syntax defined for ejb-link in the EJB 2.0 specification. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> <xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira