[
https://issues.apache.org/jira/browse/AXIS2-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Rheinheimer updated AXIS2-3726:
------------------------------------
Attachment: patch.txt
Fixed in 646963. Thanks Jarek for the fix!
I've included HUGE changes to the AddNumbersHandlerTests so that all handler
method calls are logged, both client and server side, then assertEquals with
expected results in the junit tests. It should be pretty near impossible to
regress the handler framework, or make "double calls" into it, which is what
Jarek's patch fixes.
Previous to these fixes in the AddNumbersHandlerTests, we did see occasional
bugs in the handler framework, or usage of the handler framework, that was not
caught by junit. This is a MUCH-NEEDED improvement, and will catch such
problems in the future.
There. Done. :)
> 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, patch.txt
>
>
> 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]
