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 "Mark Whitlock (JIRA)" <ax...@ws.apache.org> on 2005/03/11 12:54:52 UTC
[jira] Created: (AXISCPP-530) Look for libraries under AXISCPP_DEPLOY
Look for libraries under AXISCPP_DEPLOY
---------------------------------------
Key: AXISCPP-530
URL: http://issues.apache.org/jira/browse/AXISCPP-530
Project: Axis-C++
Type: Bug
Reporter: Mark Whitlock
Assigned to: Mark Whitlock
The dynamically loaded libraries (transport, xmlparser, etc) are by default under the directory pointed to by AXISCPP_DEPLOY, so it would be sensible to look there when loading these libraries. So the order of places to look when loading these libraries should be
1) Whatever is specified in axiscpp.conf (so the user can override any specific library)
2) If axiscpp.conf is missing, or does not specify the library, look in AXISCPP_DEPLOY/bin (windows) or AXISCPP_DEPLOY/lib (unix)
3) If the library is still not found, look for it in the library path environment variable.
--
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
[jira] Closed: (AXISCPP-530) Look for libraries under AXISCPP_DEPLOY
Posted by "Mark Whitlock (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-530?page=history ]
Mark Whitlock closed AXISCPP-530:
---------------------------------
Resolution: Won't Fix
Users have to have their AxisClient library on their library path. All the other libraries are in the same directory as the AxisClient library. Axis already looks for dynamically loaded libraries in the library path. So (assuming the user hasn't been moving Axis libraries around and assuming that they have set up their library path correctly to find the AxisClient library), the dynamically loaded libraries will be found. So the fix suggested by this JIRA is not needed and I am closing this JIRA as "won't fix".
> Look for libraries under AXISCPP_DEPLOY
> ---------------------------------------
>
> Key: AXISCPP-530
> URL: http://issues.apache.org/jira/browse/AXISCPP-530
> Project: Axis-C++
> Type: Bug
> Reporter: Mark Whitlock
> Assignee: Mark Whitlock
>
> The dynamically loaded libraries (transport, xmlparser, etc) are by default under the directory pointed to by AXISCPP_DEPLOY, so it would be sensible to look there when loading these libraries. So the order of places to look when loading these libraries should be
> 1) Whatever is specified in axiscpp.conf (so the user can override any specific library)
> 2) If axiscpp.conf is missing, or does not specify the library, look in AXISCPP_DEPLOY/bin (windows) or AXISCPP_DEPLOY/lib (unix)
> 3) If the library is still not found, look for it in the library path environment variable.
--
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
[jira] Commented: (AXISCPP-530) Look for libraries under AXISCPP_DEPLOY
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-530?page=comments#action_60652 ]
nadir amra commented on AXISCPP-530:
------------------------------------
Last option would be hard-coded paths if not found.
> Look for libraries under AXISCPP_DEPLOY
> ---------------------------------------
>
> Key: AXISCPP-530
> URL: http://issues.apache.org/jira/browse/AXISCPP-530
> Project: Axis-C++
> Type: Bug
> Reporter: Mark Whitlock
> Assignee: Mark Whitlock
>
> The dynamically loaded libraries (transport, xmlparser, etc) are by default under the directory pointed to by AXISCPP_DEPLOY, so it would be sensible to look there when loading these libraries. So the order of places to look when loading these libraries should be
> 1) Whatever is specified in axiscpp.conf (so the user can override any specific library)
> 2) If axiscpp.conf is missing, or does not specify the library, look in AXISCPP_DEPLOY/bin (windows) or AXISCPP_DEPLOY/lib (unix)
> 3) If the library is still not found, look for it in the library path environment variable.
--
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