[ http://issues.apache.org/jira/browse/AXISCPP-929?page=comments#action_12367012 ]
John Hawkins commented on AXISCPP-929: -------------------------------------- Hi Nadir, We had worked on a design that had registration of "Exception handlers" for C. If we used this method then the flow of execution would look like this create ws register exception handler for WSDL specific exceptions register exception handler for axis exceptions register exception handler for generic exceptions call method. unregister handlers if you want. however, they could simply set a flag in their handlers to say something like "now calling method Y" so that they knew what had just happened when the handler was called. This method would not require the C signatures to change. > C interfaces should capture all C++ exceptions > ---------------------------------------------- > > Key: AXISCPP-929 > URL: http://issues.apache.org/jira/browse/AXISCPP-929 > Project: Axis-C++ > Type: Bug > Components: Client - API > Reporter: nadir amra > Assignee: nadir amra > > The C interfaces should catch all C++ exceptions and provide a way to > indicate whether operation was successful or not. > This means that we may have to eliminate the dynamic generation of the C > header files based on the C++ header files since the prototypes for the calls > may not be exactly the same - i.e. return value may indicate success or > failure and if the function returned some value, the value returned on a the > C interface may become an argument that would need to be passed in. -- 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
