-
- All Known Implementing Classes:
- GenericHandler
public interface Handler
Thejavax.xml.rpc.handler.Handler
interface is required to be implemented by a SOAP message handler. ThehandleRequest
,handleResponse
andhandleFault
methods for a SOAP message handler get access to theSOAPMessage
from theSOAPMessageContext
. The implementation of these methods can modify theSOAPMessage
including the headers and body elements.- Version:
- 1.0
- Author:
- Rahul Sharma
-
-
Method Summary
All Methods Instance Methods Abstract Methods Modifier and Type Method and Description void
destroy()
Thedestroy
method indicates the end of lifecycle for a Handler instance.QName[]
getHeaders()
Gets the header blocks that can be processed by this Handler instance.boolean
handleFault(MessageContext context)
ThehandleFault
method processes the SOAP faults based on the SOAP message processing model.boolean
handleRequest(MessageContext context)
ThehandleRequest
method processes the request message.boolean
handleResponse(MessageContext context)
ThehandleResponse
method processes the response SOAP message.void
init(HandlerInfo config)
Theinit
method enables the Handler instance to initialize itself.
-
-
-
Method Detail
-
handleRequest
boolean handleRequest(MessageContext context)
ThehandleRequest
method processes the request message.- Parameters:
context
-MessageContext
parameter provides access to the request message.- Returns:
- boolean Indicates the processing mode
- Return
true
to indicate continued processing of the request handler chain. TheHandlerChain
takes the responsibility of invoking the next entity. The next entity may be the next handler in theHandlerChain
or if this handler is the last handler in the chain, the next entity is the service endpoint object. - Return
false
to indicate blocking of the request handler chain. In this case, further processing of the request handler chain is blocked and the target service endpoint is not dispatched. The JAX-RPC runtime system takes the responsibility of invoking the response handler chain next with the SOAPMessageContext. The Handler implementation class has the the responsibility of setting the appropriate response SOAP message in either handleRequest and/or handleResponse method. In the default processing model, the response handler chain starts processing from the same Handler instance (that returned false) and goes backward in the execution sequence.
- Return
- Throws:
JAXRPCException
- This exception indicates 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
- This 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 context. 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.
-
handleResponse
boolean handleResponse(MessageContext context)
ThehandleResponse
method processes the response SOAP message.- Parameters:
context
- MessageContext parameter provides access to the response SOAP message- Returns:
- boolean Indicates the processing mode
- Return
true
to indicate continued processing ofthe response handler chain. The HandlerChain invokes thehandleResponse
method on the nextHandler
in the handler chain. - Return
false
to indicate blocking of the response handler chain. In this case, no other response handlers in the handler chain are invoked.
- Return
- Throws:
JAXRPCException
- Indicates handler specific runtime error. If JAXRPCException is thrown by a handleResponse 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 runtime exception is propagated to the client code.
-
handleFault
boolean handleFault(MessageContext context)
ThehandleFault
method processes the SOAP faults based on the SOAP message processing model.- Parameters:
context
- MessageContext parameter provides access to the SOAP message- Returns:
- boolean Indicates the processing mode
- Return
true
to indicate continued processing of SOAP Fault. The HandlerChain invokes thehandleFault
method on the nextHandler
in the handler chain. - Return
false
to indicate end of the SOAP fault processing. In this case, no other handlers in the handler chain are invoked.
- Return
- Throws:
JAXRPCException
- Indicates handler specific runtime error. If JAXRPCException is thrown by a handleFault 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 JAXRPCException is propagated to the client code.
-
init
void init(HandlerInfo config)
Theinit
method enables the Handler instance to initialize itself. Theinit
method passes the handler configuration as aHandlerInfo
instance. The HandlerInfo is used to configure the Handler (for example: setup access to an external resource or service) during the initialization.In the init method, the Handler class may get access to any resources (for example; access to a logging service or database) and maintain these as part of its instance variables. Note that these instance variables must not have any state specific to the SOAP message processing performed in the various handle method.
- Parameters:
config
- Configuration for the initialization of this handler- Throws:
JAXRPCException
- If initialization of the handler fails
-
destroy
void destroy()
Thedestroy
method indicates the end of lifecycle for a Handler instance. The Handler implementation class should release its resources and perform cleanup in the implementation of thedestroy
method.- Throws:
JAXRPCException
- If any error during destroy
-
getHeaders
QName[] getHeaders()
Gets the header blocks that can be processed by this Handler instance.- Returns:
- Array of QNames of header blocks processed by this
handler instance.
QName
is the qualified name of the outermost element of the Header block.
-
-
Traduction non disponible
Les API Java ne sont pas encore traduites en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.
Version en cache
21/08/2025 19:04:58 Cette version de la page est en cache (à la date du 21/08/2025 19:04:58) afin d'accélérer le traitement.Vous pouvez activer le mode utilisateur dans le menu en haut pour afficher la version plus récente de la page.
Document créé le 18/04/2008, dernière modification le 18/08/2025
Source du document imprimé : https://www.gaudry.be/java-api-javaee-rf-javax/xml/rpc/handler/Handler.html
L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.
Références
Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.