This documentation differs from the official API. Jadeite adds extra features to the API including: variable font sizes, constructions examples, placeholders for classes and methods, and auto-generated “See Also” links. Additionally it is missing some items found in standard Javadoc documentation, including: generics type information, “Deprecated” tags and comments, “See Also” links, along with other minor differences. Please send any questions or feedback to bam@cs.cmu.edu.


javax.xml.ws
class EndpointReference

java.lang.Object extended by javax.xml.ws.EndpointReference
Direct Known Subclasses:
W3CEndpointReference

public abstract class EndpointReference
extends Object

This class represents an WS-Addressing EndpointReference which is a remote reference to a web service endpoint. See Web Services Addressing 1.0 - Core for more information on WS-Addressing EndpointReferences.

This class is immutable as the typical web service developer need not be concerned with its contents. The web service developer should use this class strictly as a mechanism to reference a remote web service endpoint. See the {@link Service} APIs that clients can use to that utilize an EndpointReference. See the {@link javax.xml.ws.Endpoint}, and {@link javax.xml.ws.BindingProvider} APIs on how EndpointReferences can be created for published endpoints.

Concrete implementations of this class will represent an EndpointReference for a particular version of Addressing. For example the {@link W3CEndpointReference} is for use with W3C Web Services Addressing 1.0 - Core Recommendation. If JAX-WS implementors need to support different versions of addressing, they should write their own EndpointReference subclass for that version. This will allow a JAX-WS implementation to create vendor specific EndpointReferences that that vendor can use to flag a different version of addressing.

Web service developers that wish to pass or return EndpointReferences in Java methods in an SEI should use concrete instances of an EndpointReference such as the W3CEndpointReference. This way the schema mapped from the SEI will be more descriptive of the type of endpoint reference being passed.

JAX-WS implementors are expected to extract the XML infoset from an EndpointReferece using the {@link EndpointReference#writeTo} method.

JAXB will bind this class to xs:anyType. If a better binding is desired, web services developers should use a concrete subclass such as {@link W3CEndpointReference}.


Constructor Summary
protected

          
 
Method Summary
 Object
getPort(Class serviceEndpointInterface, WebServiceFeature[] features)

          The getPort method returns a proxy.
static EndpointReference
readFrom(Source eprInfoset)

          Factory method to read an EndpointReference from the infoset contained in eprInfoset.
 String

          Displays EPR infoset for debugging convenience.
abstract void
writeTo(Result result)

          write this EndpointReference to the specified infoset format
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

EndpointReference

protected EndpointReference()
Method Detail

getPort

public Object getPort(Class serviceEndpointInterface,
                      WebServiceFeature[] features)
The getPort method returns a proxy. If there are any reference parameters in the EndpointReference instance, then those reference parameters MUST appear as SOAP headers, indicating them to be reference parameters, on all messages sent to the endpoint. The parameter serviceEndpointInterface specifies the service endpoint interface that is supported by the returned proxy. The EndpointReference instance specifies the endpoint that will be invoked by the returned proxy. In the implementation of this method, the JAX-WS runtime system takes the responsibility of selecting a protocol binding (and a port) and configuring the proxy accordingly from the WSDL Metadata from this EndpointReference or from annotations on the serviceEndpointInterface. For this method to successfully return a proxy, WSDL metadata MUST be available and the EndpointReference instance MUST contain an implementation understood serviceName metadata.

Because this port is not created from a Service object, handlers will not automatically be configured, and the HandlerResolver and Executor cannot be get or set for this port. The BindingProvider().getBinding().setHandlerChain() method can be used to manually configure handlers for this port.

Parameters:
serviceEndpointInterface - Service endpoint interface
features - An array of WebServiceFeatures to configure on the proxy. Supported features not in the features parameter will have their default values.
Returns:
Object Proxy instance that supports the specified service endpoint interface

readFrom

public static EndpointReference readFrom(Source eprInfoset)
Factory method to read an EndpointReference from the infoset contained in eprInfoset. This method delegates to the vendor specific implementation of the {@link javax.xml.ws.spi.Provider#readEndpointReference} method.

Parameters:
eprInfoset - The EndpointReference infoset to be unmarshalled
Returns:
the EndpointReference unmarshalled from eprInfoset never null

toString

public String toString()
Displays EPR infoset for debugging convenience.

Overrides:
toString in class Object

writeTo

public abstract void writeTo(Result result)
write this EndpointReference to the specified infoset format

Parameters:
result


This documentation differs from the official API. Jadeite adds extra features to the API including: variable font sizes, constructions examples, placeholders for classes and methods, and auto-generated “See Also” links. Additionally it is missing some items found in standard Javadoc documentation, including: generics type information, “Deprecated” tags and comments, “See Also” links, along with other minor differences. Please send any questions or feedback to bam@cs.cmu.edu.
This page displays the Jadeite version of the documention, which is derived from the offical documentation that contains this copyright notice:
Copyright 2008 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.
The official Sun™ documentation can be found here at http://java.sun.com/javase/6/docs/api/.