You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org> on 2007/02/12 15:12:05 UTC
[jira] Resolved: (AXIS2-2052) Axis2 generated message receiver
fails to throw an exception when the dispatched operation is not found...
[ https://issues.apache.org/jira/browse/AXIS2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi resolved AXIS2-2052.
-------------------------------------------------
Resolution: Fixed
throws a RuntimeException if it can not find a service
> Axis2 generated message receiver fails to throw an exception when the dispatched operation is not found...
> ----------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-2052
> URL: https://issues.apache.org/jira/browse/AXIS2-2052
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Reporter: Thilina Gunarathne
> Assigned To: Amila Chinthaka Suriarachchi
>
> I had to change the generated services.xml for some reason.. But I've made a mistake and mentioned an incorrect action to operation mapping..
> This cause the Axis2 to fail in the AddressingOutHandler with a NPE due to the returned soap envelope being NULL..
> IMHO we should throw an exception when there isn't an operation matching to the dispatched operation name...
> This can be achieved by adding an else clause to the operation dispatching logic in the invokeBuisnessLogic method...
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org