Hi Nathan, I'm not an Axis2 guru, but I would suggest that the only time that the actual response is not returned is when a fault is thrown (and conceptually the fault replaces the response in that situation). So, I would assume that ABORT or SUSPEND would stop current handler processing but still allow the response to be forwarded to the client. The difference between them sounds as if ABORT immediately stops all subsequent handler processing (that is, the chain of handlers is aborted), while SUSPEND sounds as if the current handler ceases processing but perhaps the other handlers that are called after it are allowed to proceed? (That is just a guess, I'm afraid).
If you turn on tcpmon you can see the response sent back to the client. Try dropping out of your handler's invoke() using ABORT and see what the response looks like going back. Do you have more than one handler in a chain to verify the behavior? -jeff -----Original Message----- From: Nathan Hook [mailto:[EMAIL PROTECTED] Sent: Monday, November 12, 2007 11:59 AM To: [email protected] Subject: RE: Exiting a Handler without an AxisFault Thank you for the response Jeff. So, when using Axis2 and we return either the InvocationResponse ABORT or SUSPEND will that actually return a message back to the user or does the thread of execution just completely stop? Here is our goal: To do data validation in our handler and return a formated message (not an AxisFault), to our clients. They (our clients) have shown a preference to get a formated message instead of AxisFaults. When returning an IvocationResponse ABORT or SUSPEND can a message be sent back to the client? Thanks for your time! > Subject: RE: Exiting a Handler without an AxisFault > Date: Mon, 12 Nov 2007 09:58:19 -0500 > From: [EMAIL PROTECTED] > To: [email protected] > > Didn't anybody reply?? > Ok, here's what I think is the correct answer. > Yes. In the interface javax.xml.rpc.handler.Handler, the two most important > methods are handelRequest() and handleResponse(). Both return a boolean. If > you return a false, then all handler processing after this handler is > truncated, that is, any other handlers in the chain will not be called. > (whereas returning true indicates that this handler did its processign > successfully and ran into no prob;ems and please pass the messaeg context > onto the next handler in the chain). Also, obviosuly throwing a fault also > truncates further handler processing. > Now, that's the JAX-RPC 1.1 standard. > > In the JAX-WS specification, the interface javax.xml.ws.handler.Handler has > the expected handleMessage() method, which also returns a boolean. It has > pretty much the same semantics as the JAX-RPC handleRequest() and > handleResponse() methods above. > > Fine, but what about Axis2? > I think in your handler class, you should return: > new InvocationResponse(2, "InvocationResponse.ABORT") > from the invoke() method. (If that doesn't work, try returning new > InvocationResponse(1, "InvocationResponse.SUSPEND"), but I think ABORT should > work). > -jeff > > > > -----Original Message----- > From: Nathan Hook [mailto:[EMAIL PROTECTED] > Sent: Friday, November 09, 2007 4:58 PM > To: [email protected] > Subject: Exiting a Handler without an AxisFault > > > So, I'm changing up the way I word my question... > > Is there a way to exit out of a handler that discontinues the normal > execution to the next handler (returning a message to the calling client) > without throwing an AxisFault? > > Thank you for your time. > _________________________________________________________________ > Help yourself to FREE treats served up daily at the Messenger Café. Stop by > today. > http://www.cafemessenger.com/info/info_sweetstuff2.html?ocid=TXT_TAGLM_OctWLtagline > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > _________________________________________________________________ Help yourself to FREE treats served up daily at the Messenger Café. Stop by today. http://www.cafemessenger.com/info/info_sweetstuff2.html?ocid=TXT_TAGLM_OctWLtagline --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
