axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-2052) Axis2 generated message receiver fails to throw an exception when the dispatched operation is not found...
Date Mon, 12 Feb 2007 14:12:05 GMT

     [ 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


Mime
View raw message