[jira] Closed: (AXISCPP-383) Exceptoin msgs should tell you what file is missing

["Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>]

     [ http://issues.apache.org/jira/browse/AXISCPP-383?page=history ]
     
Samisa Abeysinghe closed AXISCPP-383:
-------------------------------------

     Resolution: Fixed
    Fix Version: 1.5 Final

With the use of PLATFORM_LOADLIB_ERROR to explain the load error this problems seem to have gone away.

Transport factory and paser factory was already passing PLATFORM_LOADLIB_ERROR to the exception deail.

I did update channel factory to do the same.

Now it gives out following detail:

Parser:
Exception : DLOPEN FAILED in loading parser library /home/obj/bin/libaxis_xercesc.so: cannot open shared object file: No such file or directory

Transport:
Exception : DLOPEN FAILED in loading transport library /home/obj/bin/libhttp_transports.so: cannot open shared object file: No such file or directory

Channel:
Exception : DLOPEN FAILED in loading channel library /home/obj/bin/libhttp_channelc.so: cannot open shared object file: No such file or directory


> Exceptoin msgs should tell you what file is missing
> ---------------------------------------------------
>
>          Key: AXISCPP-383
>          URL: http://issues.apache.org/jira/browse/AXISCPP-383
>      Project: Axis-C++
>         Type: Bug
>   Components: Configuration
>     Versions: 1.4 Final
>     Reporter: John Hawkins
>     Assignee: Samisa Abeysinghe
>     Priority: Minor
>      Fix For: 1.5 Final

>
> When an exception message is blown e.g. parser library fails to load. We should put out what the library was that it was trying to load eg. Parser library 'parserlibpath' failed to load.

-- 
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