[ 
https://issues.apache.org/jira/browse/AXIS2-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587690#action_12587690
 ] 

Mike Rheinheimer commented on AXIS2-3726:
-----------------------------------------

I don't see anything wrong with your patch, but I can't figure out why it is 
necessary in the first place.  We have tests that check the scenario you 
describe:

In jaxws/test:
org.apache.axis2.jaxws.handler.testHandleMessage_false1
org.apache.axis2.jaxws.handler.testHandleMessage_protocolex_false
org.apache.axis2.jaxws.handler.testHandleMessage_protocolex_protocolex
org.apache.axis2.jaxws.handler.testHandleMessage_protocolex_runtimeex

In jaxws-integration:
org.apache.axis2.jaxws.sample.testAddNumbersHandlerWithFault

> All outbound handlers are invoked when an inbound handler throws exception or 
> returns false
> -------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-3726
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3726
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Jarek Gawor
>             Fix For: 1.4, nightly
>
>         Attachments: AXIS2-3726.patch
>
>
> All outbound handlers are getting invoked even though an inbound handler 
> threw an exception or returned false from its handleMessage() method (on the 
> server side).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to