axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Dick (JIRA)" <>
Subject [jira] Commented: (AXISCPP-913) couldnt call axis c++ webservice from a client ( warning: /axiscpp.conf not found)
Date Mon, 23 Jan 2006 09:39:10 GMT
    [ ] 

Adrian Dick commented on AXISCPP-913:

You application containing the generated client stubs MUST have the Axis C++ runtime libraries
- if you wish to minimise the install, the libraries required for the client are:  axis_client,
HTTPTransport, HTTPChannel, (optionally) HTTPSSLChannel and AxisXMLParserXerces (possibly
renamed to AxisXMLParser to avoid the need for axiscpp.conf), and also the Xerces 2.2.0 libraries.

You do NOT require Apache and the web service implementation to be present on the same system,
they can be hosted remotely.

If you are unable to connect remotely, check your application is using the correct endpoint
URI (if not explicitely provided by invoking code, the generated stubs will use the value
from the WSDL file), if this is still failing ensure the service is correctly running and
you don't have any connection issues (firewalls, etc.)

> couldnt call axis c++ webservice  from a client ( warning: /axiscpp.conf not found)
> -----------------------------------------------------------------------------------
>          Key: AXISCPP-913
>          URL:
>      Project: Axis-C++
>         Type: Task
>   Components: Client - Stub
>     Versions: 1.5 Beta
>  Environment: windows 2000, apache 2.0.55 and axis c++ 1.5 version
>     Reporter: mohan Goud Devanoor
>     Priority: Critical

> hello all,
> can any one help me please. i have installed apache 2.0.55 and axis c++ 1.5 version .
The sample calculator.exe runs perfectly on my system. but when i copy it to other system
and run giving endpoint url, it gives an error message
> Message:
> warning configuration file was not found ( /axiscpp.conf)
> Using default values
> Exception : DLOPEN failed in loading parser library..
> NOTE: when i copy all the parser libraries to that system then it works giving only the
> Exception: 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message