axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mohan Goud Devanoor (JIRA)" <>
Subject [jira] Commented: (AXISCPP-913) couldnt call axis c++ webservice from a client ( warning: /axiscpp.conf not found)
Date Fri, 20 Jan 2006 10:43:42 GMT
    [ ] 

mohan Goud Devanoor commented on AXISCPP-913:

hi Adrian,
ya dats fine. It was AxisXmlParserXerces.dll and as mentioned in wininstall manual i renamed
it to AxisXmlParser.dll. earlier itself, and i also had renamed 
axiscpp.conf_win to axiscpp.conf and 
server.wsdd_win to server.wsdd as mentioned in manual.. 
still getting the same warning and Exception.

Let me make u  one thing clear.
I have Apache2.x and axis  c++ 1.5 (Binary version zipped to my system) version in my system.
we have sample server and client programs. I hav Rebuid the client calculator sample and got
the exe file(calculator.exe) . It  works fine when run on my system.
when i copy the exe file to athor system ( This system does not have any Apache or Axis c++
Installed) then it shows the WARNING and EXCEPTION message. 

Please help me out..

> 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