[ http://issues.apache.org/jira/browse/AXISCPP-237?page=all ] Mark Whitlock reopened AXISCPP-237: -----------------------------------
Jeff Clary wrote on the mailing list... > One more thing. The JIRA bug AXISCPP-237 has a comment at > the bottom that mentions a memory deallocation error that > happens whenever an AxisEngineException constructed with a > non-allocated message is thrown. This happens in Windows > whenever LoadLibrary fails, and could cause a Windows > program to crash. Should that be opened as a new bug? I have checked in the code and this still is a problem so I am reopening this defect on Nadir's and Jeff's advice. > dlopen failures should show reason for failure > ---------------------------------------------- > > Key: AXISCPP-237 > URL: http://issues.apache.org/jira/browse/AXISCPP-237 > Project: Axis-C++ > Type: Improvement > Environment: All > Reporter: Andrew Perry > Priority: Minor > > When a dlopen() error occurs a message like "DLOPEN FAILED in loading parser > library" is exception message thrown. For problem determination it would be > much more beneficial to output the reason for failure too, i.e. the output of > dlerror(). > The AxisEngineException code already has support for this, but it hasn't been > implemented in XMLParserFactory.cpp, SOAPTransportFactory.cpp or > HandlerLoader.cpp, where a dlerror() can just be added to the throw > AxisEngineException statement. -- 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
