ServiceDescriptionImpl(URL wsdlURL, QName serviceQName, Class serviceClass) This is (currently) the client-side-only constructor Construct a service description hierachy
based on WSDL (may be null), the Service class, and a service QName.
Parameters: wsdlURL - The WSDL file (this may be null). Parameters: serviceQName - The name of the service in the WSDL.
ServiceDescriptionImpl(URL wsdlURL, QName serviceQName, Class serviceClass)(Code)
This is (currently) the client-side-only constructor Construct a service description hierachy
based on WSDL (may be null), the Service class, and a service QName.
Parameters: wsdlURL - The WSDL file (this may be null). Parameters: serviceQName - The name of the service in the WSDL. This can not be null since ajavax.xml.ws.Service can not be created with a null service QName. Parameters: serviceClass - The JAX-WS service class. This could be an instance ofjavax.xml.ws.Service or a generated service subclass thereof. This willnot be null.
This is (currently) the service-provider-side-only constructor. Create a service Description
based on a service implementation class
Parameters: serviceImplClass -
This is (currently) the service-provider-side-only constructor. Create a service Description
based on a service implementation class
Parameters: serviceImplClass -
Returns a schema derived java class containing the the handler configuration filel
HandlerChainsType This is the top-level element for the Handler configuration file
public Definition getWSDLGeneratedDefinition()(Code)
Returns the WSDL definiton as created by calling the WSDL generator. This will be null
unless the WSDL definition provided by the metadata is incomplete
Update or create an EndpointDescription. Updates to existing EndpointDescriptons will be
based on the SEI class and its annotations. Both declared ports and dynamic ports can be
updated. A declared port is one that is defined (e.g. in WSDL or via annotations); a dyamic
port is one that is not defined (e.g. not via WSDL or annotations) and has been added via
Serivce.addPort.
Notes on how an EndpointDescription can be updated or created: 1) Service.createDispatch can
create a Dispatch client for either a declared or dynamic port 2) Note that creating a
Dispatch does not associate an SEI with an endpoint 3) Service.getPort will associate an SEI
with a port 4) A getPort on an endpoint which was originally created for a Distpatch will
update that EndpointDescription with the SEI provided on the getPort 5) Service.getPort can
not be called on a dynamic port (per the JAX-WS spec) 6) Service.addPort can not be called
for a declared port
Parameters: sei - This will be non-null if the update is of type GET_PORT; it will be null ifthe update is ADD_PORT or CREATE_DISPATCH Parameters: portQName - Parameters: updateType - Indicates what is causing the update GET_PORT is an attempt to get adeclared SEI-based port ADD_PORT is an attempt to add a previouslynon-existent dynamic port CREATE_DISPATCH is an attempt to create aDispatch-based client to either a declared port or a pre-existing dynamicport.
