An OperationDescripton corresponds to a method on an SEI. That SEI could be explicit (i.e.
WebService.endpointInterface=sei.class) or implicit (i.e. public methods on the service
implementation are the contract and thus the implicit SEI). Note that while
OperationDescriptions are created on both the client and service side, implicit SEIs will only
occur on the service side.
OperationDescriptons contain information that is only relevent for and SEI-based service, i.e.
one that is invoked via specific methods. This class does not exist for Provider-based services
(i.e. those that specify WebServiceProvider)
OperationDescription details
CORRESPONDS TO: A single operation on an SEI (on both Client and Server)
AXIS2 DELEGATE: AxisOperation
CHILDREN: 0..n ParameterDescription
0..n FaultDescription (Note: Not fully implemented)
ANNOTATIONS:
WebMethod [181]
SOAPBinding [181]
Oneway [181]
WebResult [181]
RequestWrapper [224]
ResponseWrapper [224]
WSDL ELEMENTS:
operation
getMethodFromServiceImpl(Class serviceImpl) Service implementation side only! Given a service implementation class, find the method on
that class that corresponds to this operation description.
getSEIMethod() Client side and non-DBC service side only! Return the SEI method for which a
service.getPort(Class SEIClass) created the EndpointDescriptionInterface and the associated
OperationDescriptions.
getSyncOperation() For JAX-WS client-side async operations, this will return the corresponding sync
OperationDescription.
Note that if this method is used within the metadata layer, it is possible that it will return
null.
Service implementation side only! Given a service implementation class, find the method on
that class that corresponds to this operation description. This is necessary because on the
service impl side, the OperationDescriptions can be built using byte-scanning and without the
class actually having been loaded.
Parameters: serviceImpl -
the class name of the wrapper class. NOTE: This method will return null if therequest wrapper class is not known during the description layer processing. In suchcases the implementation may use proprietary code to find the class. For example,JAXWS may look for a matching class in the sei package, in a special jaxws package orproceed without the class name
the class name of the wrapper class. NOTE: This method will return null if therequest wrapper class is not known during the description layer processing. In suchcases the implementation may use proprietary code to find the class. For example,JAXWS may look for a matching class in the sei package, in a special jaxws package orproceed without the class name
Return the actual Class of the type. For a JAX-WS async return type of Response or
AsyncHandler, the class associated with is returned. For non-JAX-WS async returns,
the class associated with the return type is returned. Note that for a Generic return type,
such as List, the class associated with List will be returned.
actual Class
Return the Class of the return type. For JAX-WS async returns of type Response or
AsyncHandler, the class associated with Response or AsyncHanler respectively is returned.
To get the class associated with
Class See Also: getResultActualType()
Client side and non-DBC service side only! Return the SEI method for which a
service.getPort(Class SEIClass) created the EndpointDescriptionInterface and the associated
OperationDescriptions. Returns null on the service implementation side.
getSoapBindingParameterStyle
public javax.jws.soap.SOAPBinding.ParameterStyle getSoapBindingParameterStyle()(Code)
getSoapBindingStyle
public javax.jws.soap.SOAPBinding.Style getSoapBindingStyle()(Code)
getSoapBindingUse
public javax.jws.soap.SOAPBinding.Use getSoapBindingUse()(Code)
For JAX-WS client-side async operations, this will return the corresponding sync
OperationDescription.
Note that if this method is used within the metadata layer, it is possible that it will return
null. That will happen if the metadata layer is constructed from annotations on the SEI
(not WSDL). In that case, it is possible that the async methods on the SEI are processed
before the sync method. In that case, there will be no sync method yet. If this method
is called outside the metadata layer, then if the async methods exist, the sync method
should also exist.
OperationDescription corresponding to the sync operation, or null (see note above).
Answer if this operation corresponds to the JAX-WS Client-only async methods. These methods
are of the form: javax.xml.ws.Response method(...) java.util.concurrent.Future
method(..., javax.xml.ws.AsyncHandler)