Modifier and Type | Field and Description |
---|---|
static int |
DOES_NOT_EXIST |
static int |
METHOD_READY |
Constructor and Description |
---|
HandlerWrapper(Handler handler)
Delegate to the given handler
|
Modifier and Type | Method and Description |
---|---|
void |
destroy()
The destroy method indicates the end of lifecycle for a Handler instance.
|
QName[] |
getHeaders()
Gets the header blocks processed by this Handler instance.
|
int |
getState()
Get the current state
|
String |
getStateAsString()
Get the current state as string
|
boolean |
handleFault(MessageContext msgContext)
The handleFault method processes the SOAP faults based on the SOAP message processing model.
|
boolean |
handleRequest(MessageContext msgContext)
The handleRequest method processes the request message.
|
boolean |
handleResponse(MessageContext msgContext)
The handleResponse method processes the response SOAP message.
|
int |
hashCode()
Returns a hash code value for the object.
|
void |
init(HandlerInfo config)
The init method enables the Handler instance to initialize itself.
|
String |
toString()
Returns a string representation of the object.
|
public static final int DOES_NOT_EXIST
public static final int METHOD_READY
public HandlerWrapper(Handler handler)
public int getState()
public String getStateAsString()
public QName[] getHeaders()
getHeaders
in interface Handler
public void init(HandlerInfo config) throws JAXRPCException
init
in interface Handler
config
- HandlerInfo configuration for the initialization of this handlerJAXRPCException
- - if initialization of the handler failspublic void destroy() throws JAXRPCException
destroy
in interface Handler
JAXRPCException
- - if there was any error during destroypublic boolean handleRequest(MessageContext msgContext) throws JAXRPCException, SOAPFaultException
handleRequest
in interface Handler
msgContext
- MessageContext parameter provides access to the request message.JAXRPCException
- - indicates a handler-specific runtime error.
If JAXRPCException is thrown by a handleRequest method, the HandlerChain terminates the further processing of this handler chain.
On the server side, the HandlerChain generates a SOAP fault that indicates that the message could not be processed
for reasons not directly attributable to the contents of the message itself but rather to a runtime error during
the processing of the message. On the client side, the exception is propagated to the client codeSOAPFaultException
- - indicates a SOAP fault. The Handler implementation class has the the responsibility
of setting the SOAP fault in the SOAP message in either handleRequest and/or handleFault method.
If SOAPFaultException is thrown by a server-side request handler's handleRequest method, the HandlerChain
terminates the further processing of the request handlers in this handler chain and invokes the handleFault
method on the HandlerChain with the SOAP message msgContext. Next, the HandlerChain invokes the handleFault method
on handlers registered in the handler chain, beginning with the Handler instance that threw the exception and
going backward in execution. The client-side request handler's handleRequest method should not throw the SOAPFaultException.public boolean handleResponse(MessageContext msgContext)
handleResponse
in interface Handler
msgContext
- MessageContext parameter provides access to the response SOAP messagepublic boolean handleFault(MessageContext msgContext)
handleFault
in interface Handler
msgContext
- MessageContext parameter provides access to the SOAP messagepublic int hashCode()
Copyright © 2018 JBoss by Red Hat. All rights reserved.