[ http://issues.apache.org/jira/browse/AXISCPP-497?page=comments#action_60107 ] Mark Whitlock commented on AXISCPP-497: ---------------------------------------
Hi Samisa, There are several problems here. Fred put in a fix under AXISCPP-478/490 into Call::setTransportProperty to convert a HTTPTransportException into a AxisGenException because by the time the client application has caught the exception, the transport library will have been unloaded and so calling any methods on the HTTPTransportException would SIGSEGV. Copying the exception data into a AxisGenException solves this problem. This problem is not fixed in Stub::setTransportProperty. There is also various other logic in Call::setTransportProperty that is not in Stub::setTransportProperty. I think this method should behave the same on Stub and Call (and I hate copying code since it gets out of step) so I would prefer to call Call::setTransportProperty from Stub::setTransportProperty. Unfortunately I now realise this is not so simple because Call::setTransportProperty takes a AXIS_TRANSPORT_INFORMATION_TYPE whereas Stub::setTransportProperty takes a char*. SOAPTransport has both signatures and they behave differently. I propose that setTransportProperty (on Call and Stub) should take a AXIS_TRANSPORT_INFORMATION_TYPE only (not a char*). What do you think? This would alter the TestTransportProperties test. > Problems with Stub::setTransportProperty > ---------------------------------------- > > Key: AXISCPP-497 > URL: http://issues.apache.org/jira/browse/AXISCPP-497 > Project: Axis-C++ > Type: Bug > Reporter: Mark Whitlock > Assignee: Mark Whitlock > > The exception processing in Call::setTransportProperty is not in > Stub::setTransportProperty. Stub::setTransportProperty should just call > Call::setTransportProperty instead of SOAPTransport::setTransportProperty. > Also the message is new[]'ed in Call but delete'd in AxisGenException. This > will fail on Linux, where it should be delete[]'ed. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
