You are viewing a plain text version of this content. The canonical link for it is here.

Posted to c-dev@axis.apache.org by "Andrew Perry (JIRA)" <ax...@ws.apache.org> on 2004/11/15 10:46:26 UTC

[jira] Resolved: (AXISCPP-237) dlopen failures should show reason for failure

     [ http://nagoya.apache.org/jira/browse/AXISCPP-237?page=history ]
     
Andrew Perry resolved AXISCPP-237:
----------------------------------

    Resolution: Fixed

Added #define statements into the PlatformSpecific header files that allow the shared library open failure messages to be displayed if available.

> dlopen failures should show reason for failure
> ----------------------------------------------
>
>          Key: AXISCPP-237
>          URL: http://nagoya.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://nagoya.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