@(#)javaee_web_services_client_1_2.xsds 1.19 02/13/06 Copyright 2003-2006 Sun Microsystems, Inc. 4150 Network Circle Santa Clara, California 95054 U.S.A All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and other countries. This document and the technology which it describes are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE, JavaServer Pages, Enterprise JavaBeans and the Java Coffee Cup logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Federal Acquisitions: Commercial Software - Government Users Subject to Standard License Terms and Conditions. (C) Copyright International Business Machines Corporation 2002 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. The service-endpoint-interface element defines a fully qualified Java class that represents the Service Endpoint Interface of a WSDL port. 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 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. Defines the name of the handler. The name must be unique within the module. The service-ref element declares a reference to a Web service. It contains optional description, display name and icons, a declaration of the required Service interface, an optional WSDL document location, an optional set of JAX-RPC mappings, an optional QName for the service element, an optional set of Service Endpoint Interfaces to be resolved by the container to a WSDL port, and an optional set of handlers. The service-ref-name element declares logical name that the components in the module use to look up the Web service. It is recommended that all service reference names start with "service/". The service-interface element declares the fully qualified class name of the JAX-RPC Service interface the client depends on. In most cases the value will be javax.xml.rpc.Service. A JAX-RPC generated Service Interface class may also be specified. The service-ref-type element declares the type of the service-ref element that is injected or returned when a JNDI lookup is done. This must be either a fully qualified name of Service class or the fully qualified name of service endpoint interface class. This is only used with JAX-WS runtime where the corresponding @WebServiceRef annotation can be used to denote both a Service or a Port. If this is not specified, then the type of service-ref element that is injected or returned when a JNDI lookup is done is always a Service interface/class. The wsdl-file element contains the URI location of a WSDL file. The location is relative to the root of the module. The jaxrpc-mapping-file element contains the name of a file that describes the JAX-RPC mapping between the Java interaces used by the application and the WSDL description in the wsdl-file. The file name is a relative path within the module file. This is not required when JAX-WS based runtime is used. The service-qname element declares the specific WSDL service element that is being refered to. It is not specified if no wsdl-file is declared. 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. Declares the handler for a port-component. Handlers can access the init-param name/value pairs using the HandlerInfo interface. If port-name is not specified, the handler is assumed to be associated with all ports of the service. To be used with JAX-RPC based runtime only. To be used with JAX-WS based runtime only. The handler-chain element defines the handlerchain. Handlerchain can be defined such that the handlers in the handlerchain operate,all ports of a service, on a specific port or on a list of protocol-bindings. The choice of elements service-name-pattern, port-name-pattern and protocol-bindings are used to specify whether the handlers in handler-chain are for a service, port or protocol binding. If none of these choices are specified with the handler-chain element then the handlers specified in the handler-chain will be applied on everything. The handler-chains element defines the handlerchains associated with this service or service endpoint. Declares the handler for a port-component. Handlers can access the init-param name/value pairs using the HandlerInfo interface. If port-name is not specified, the handler is assumed to be associated with all ports of the service. Used in: service-ref Defines the name of the handler. The name must be unique within the module. Defines a fully qualified class name for the handler implementation. Defines the QName of a SOAP header that will be processed by the handler. The soap-role element contains a SOAP actor definition that the Handler will play as a role. The port-name element defines the WSDL port-name that a handler should be associated with. Defines the type that is used for specifying tokens that start with ## which are used to alias existing standard protocol bindings and support aliases for new standard binding URIs that are introduced in future specifications. The following tokens alias the standard protocol binding URIs: ##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http" ##SOAP11_HTTP_MTOM = "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true" ##SOAP12_HTTP = "http://www.w3.org/2003/05/soap/bindings/HTTP/" ##SOAP12_HTTP_MTOM = "http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true" ##XML_HTTP = "http://www.w3.org/2004/08/wsdl/http" Defines the type used for specifying a list of protocol-bindingType(s). For e.g. ##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP Defines the type used for specifying the URI for the protocol binding used by the port-component. For portability one could use one of the following tokens that alias the standard binding types: ##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM ##XML_HTTP Other specifications could define tokens that start with ## to alias new standard binding URIs that are introduced. This is used to specify the QName pattern in the attribute service-name-pattern and port-name-pattern in the handler-chain element For example, the various forms acceptable here for service-name-pattern attribute in handler-chain element are : Exact Name: service-name-pattern="ns1:EchoService" In this case, handlers specified in this handler-chain element will apply to all ports with this exact service name. The namespace prefix must have been declared in a namespace declaration attribute in either the start-tag of the element where the prefix is used or in an an ancestor element (i.e. an element in whose content the prefixed markup occurs) Pattern : service-name-pattern="ns1:EchoService*" In this case, handlers specified in this handler-chain element will apply to all ports whose Service names are like EchoService1, EchoServiceFoo etc. The namespace prefix must have been declared in a namespace declaration attribute in either the start-tag of the element where the prefix is used or in an an ancestor element (i.e. an element in whose content the prefixed markup occurs) Wild Card : service-name-pattern="*" In this case, handlers specified in this handler-chain element will apply to ports of all service names. The same can be applied to port-name attribute in handler-chain element.