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 "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org> on 2005/06/30 12:04:58 UTC

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

    [ http://issues.apache.org/jira/browse/AXISCPP-237?page=comments#action_12314749 ] 

Samisa Abeysinghe commented on AXISCPP-237:
-------------------------------------------

I have updated the exception handling code to append the errorno in addition to dlerror.
Please chek if those fixes solve the problems here.

Dushshantha is working on AXISCPP-707 which deals with the exception error.

> 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