Are You Recruiter/Hiring Manager

*Filter candidates using TestYourCandidate.com and save 80% time ( saving time for recruiters and interviewers)
*More than 50% candidates can be filtered on Candidate Screening online tests
*Inbuilt exams are available in library, created and tested by experts Try Today...

The handleRequest, handleResponse and handleFault methods
for a SOAP message handler get access to the SOAPMessage from the SOAPMessageContext. The
implementation of these methods can modify the SOAPMessage including the headers and body elements.

The handleRequest method performs one of the following steps after performing handler specific
processing of the request SOAP message:

Return true to indicate continued processing of the request handler chain. The
HandlerChain takes the responsibility of invoking the next entity. The next entity
may be the next handler in the HandlerChain or if this handler is the last handler in
the chain, the next entity is the target service endpoint. The mechanism for dispatch
or invocation of the target service endpoint depends on whether the request HandlerChain is
on the client side or service endpoint side.

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 appropriate SOAPMessageContext. The
Handler implementation class has the responsibility of setting the response SOAP message in
the handleRequest method and perform additional processing in the
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.

Throw the javax.xml.rpc.soap.SOAPFaultException to indicate a SOAP fault. The
Handler implementation class has 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.
Refer to the SOAP specification for details on the various SOAP faultcode values
and corresponding specification.

Throw the JAXRPCException or any other RuntimeException for any 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. Refer to the SOAP specification for details on the
various SOAP faultcode values. On the client side, the
JAXRPCException or runtime exception is propagated to the client code as
a RemoteException or its subtype.

The handleResponse method performs the processing of the SOAP response message. It does one of the
following steps after performing its handler specific processing of the SOAP message:

Return true to indicate continued processing of the response handler chain. The
HandlerChain invokes the handleResponse method on the next
Handler 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. On the service endpoint side, this may be
useful if response handler chooses to issue a response directly without requiring other response handlers to
be invoked.

Throw the JAXRPCException or any other RuntimeException for any handler
specific runtime error. If JAXRPCException is thrown by the 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 JAXRPCException or runtime exception is propagated to the
client code as a RemoteException or its subtype.

The handleFault method performs the SOAP fault related processing. The JAX-RPC
runtime system should invoke the handleFault method if a SOAP fault needs to be
processed by either client-side or server-side handlers. The handleFault method does
one of the following steps after performing handler specific processing of the SOAP fault:

Return true to indicate continued processing of the fault handlers in the handler
chain. The HandlerChain invokes the handleFault method on the next
Handler in the handler chain.

Return false to indicate blocking of the fault processing in the handler chain. In this
case, no other handlers in the handler chain are invoked. The JAX-RPC runtime system takes the further
responsibility of processing the SOAP message.

Throw JAXRPCException or any other RuntimeException for any handler specific
runtime error. If JAXRPCException is thrown by the 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 or runtime exception is propagated to the client code as a
RemoteException or its subtype.

Please note that when a JAXRPCException or RuntimeException raised on the server is
converted to a SOAP fault for the purpose of being transmitted to the client, there are no guarantees that any of the
information it contains will be preserved.

The following shows an example of the SOAP fault processing. In this case, the request handler Handler_2 on
the server side throws a SOAPFaultException in the handleRequest method:

Handler_1.handleRequest

Handler_2.handleRequest -> throws SOAPFaultException

Handler_2.handleFault

Handler_1.handleFault

The information you are posting should be related to java and ORACLE technology. Not political.