[ http://issues.apache.org/jira/browse/AXIS-1908?page=comments#action_12316477 ]
Bobby Lawrence commented on AXIS-1908: -------------------------------------- OK - Sorry about that. I got this issue mixed up with another: AXIS-1909. On the other issue (not this one), but for AXIS-1909, I think the Exception should ALWAYS be thrown because it causes problems when using the SAAJ API....you don't know if a Fault was returned from the server. For this issue (AXIS-1908), it seems that because the code is being executed inside another thread, you can't throw an AxisFault....the only way would be to throw some subclass of runtime exception. Why does this code need to run in a seperate thread? Instead of creating a new Runnable and starting a new Thread with that Runnable, can't Axis just call service.getEngine().invoke( msgContext );? If the method was implemented this way without the new Thread, the invokeEngineOneWay method could throw an AxisFault. > 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
