axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "thomas schaedler (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Commented: (AXIS-1908) Exception Handling in org.apache.axis.client.Call.invokeEngineOneWay
Date Fri, 22 Jul 2005 09:30:46 GMT
    [ http://issues.apache.org/jira/browse/AXIS-1908?page=comments#action_12316454 ] 

thomas schaedler commented on AXIS-1908:
----------------------------------------

IMHO this is more than an improvement. It makes it impossible to implement reliable messaging
- with an own handler when you don't get any exception in case of an error. We need to implement
transactions consisting of multiple steps, whereas on step is sending a message.

This makes it impossible to have reliable oneway communication, even if the transport is reliable
(MQ), because the intermediate axis-step breaks the whole exception handling.

> Exception Handling in org.apache.axis.client.Call.invokeEngineOneWay
> --------------------------------------------------------------------
>
>          Key: AXIS-1908
>          URL: http://issues.apache.org/jira/browse/AXIS-1908
>      Project: Apache Axis
>         Type: Improvement
>   Components: Basic Architecture
>  Environment: Windows XP Pro, Java 1.4.2, Axis 1.2 RC3
>     Reporter: Bobby Lawrence
>     Priority: Minor

>
> It would be nice if the private method invokeEngineOneWay threw a runtime subclass of
AxisFault or something instead of just catching it an logging.
> I see that it has 'todo' comments around it, I thought that reworking the architecture
slightly to have a runtime version of an AxisFault might help.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message