axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Perry (JIRA)" <>
Subject [jira] Commented: (AXISCPP-237) dlopen failures should show reason for failure
Date Wed, 10 Nov 2004 18:41:24 GMT
     [ ]
Andrew Perry commented on AXISCPP-237:

Now that the code has been re-factored to use the platforms directory for platform specific
code and use #defines in the code, a new #define could be added called PLATFORM_LOADLIB_ERROR
which can be set to lt_dlerror() or dlerror() for unix and "" for other platforms, or whatever
routine exists or could be written to show a reason for failure on the other platforms.

The AxisEngineException(const int, char*); method could then be called with PLATFORM_LOADLIB_ERROR
as the char* parameter. For platforms that do not have an error routine will pass in the empty
string. This will greatly simplify fault tracking for a user. At the very least this should
be added to the TRACE messages.

Another alternative is to only define the PLATFORM_LOADLIB_ERROR for platforms that support
it and ifdef the throw call. This will prevent the "" empty string being passed as a parameter.

throw AxisEngineException(...., PLATFORM_LOADLIB_ERROR);
throw AxisEngineException(....);

> dlopen failures should show reason for failure
> ----------------------------------------------
>          Key: AXISCPP-237
>          URL:
>      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:
If you want more information on JIRA, or have a bug to report see:

View raw message