We had a similar issue. We resolved it by modifying the source code and
compiling our own Axis binaries.
Add the following
axis\include\axis\client\Call.hpp:
/**
* Returns the DeSerialized response header.
*/
IHeaderBlock* getDeSerHeaderBlock(const AxisChar * pName, const AxisCh
C++.
This is actual response from PowerCenter:
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
http://www.informatica.com/wsh";>
1d2b79bbe22efa2011f4cf3a9db
Are you using Axis2/c? or Axis c++?
From: Golikov, Vassili [mailto:vassili.goli...@credit-suisse.com]
Sent: Friday, February 06, 2009 2:50 PM
To: axis-c-user@ws.apache.org
Subject: How to get a value from SOAP header using Axis C++?
My apps server needs to talk to Informatica WS. It sends a sess
My apps server needs to talk to Informatica WS. It sends a session ID in
the header which should be retrieved and used in all their requests. How
can I get this value from a SOAP header?
Vassilli Golikov
Equity Derivatives IT
Credit Suisse Securities (USA) LLC
One Madison Avenue
10th Floor
New Yor
It was my problem. I forgot to multiply by 1000 when setting time-out in
milliseconds.
Regards,
Raghu
From: Raghu Udupa [mailto:rud...@easylink.com]
Sent: Friday, February 06, 2009 9:45 AM
To: Apache AXIS C User List
Subject: RE: Spurious client time out e
Ryan,
Just send the stuff to me.I think you can also attach files to the
jira.. If not, I can attach the files when you send them. thanks.
Nadir Amra
"McCullough, Ryan" wrote on 02/05/2009 07:39:02
PM:
> [image removed]
>
> RE: Axis C++ 1.6 client app connecting using https through ht
Hi,
This problem happens only when I use HTTP protocol. With HTTPS every
thing works fine. One message is sent and one is received.
I am using Axis2C/1.5.0 on a Linux server as a client communicating to a
Web service. Each message is delivered to a possibly different web
service through a
Hi,
I am using Axis2C/1.5.0 on a Linux server as a client communicating to a
Web service. Each message is delivered to a possibly different web
service through a separate process. The process communicates either via
http or https depending on remote web service configuration
On couple of oc
