Hi
You can just set the SOAPAction in the client main program by using
following code.
ws->setTransportProperty("SOAPAction" , "SERVICE#METHOD");
here 'ws' is your service stub.
Regards,
Dushshantha
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday,
It looks like the HTML encoding's right (as far as I know). The bit
about URL encoding was a red herring. The guy thought HTML encoding was
called URL encoding. He's talking about the same thing I am (< ,
etc), so I think it's not an issue.
Thanks,
Rob
-Original Message-
From: Samisa A
Hi everybody,
I have an axis c++ 1.5 server and client.
The server has two methods. When I call
the second method (after having called the
first) my server crashes. Apparently this
line in the client causes the problem:
if (NULL==m_pCall->getTransportProperty("SOAPAction",false))
{
m_pCall->set
I was asking for the SOAP
message to see if there is any connection related HTTP headers like
“connection: close”, which Axis C++ is capable of handling.
The “FIN” is
at TCP/IP level and this seems to be not handled by the transport – so
you are correct.
The problem is that
because
I have installed a network analizer: http://www.ethereal.com/ and checked
the TCP/IP packages sent between the client and server. After about 10
seconds after the client receives the response from the server, the server send
a TPC/IP package "FIN" in which it announce the client that it is cl
The client is capable of re-using the
connection – this has been tested to work.
What do you men by “the server sends
a FIN package”?
Could you please send the request and
response SOAP messages?
Thanks,
Samisa…
-Original Message-
From: Popa Horia
[mailto:[EMAIL PR
I have a Java Axis server
and a client in C++, client generated by the Axis C framework. The
client runs on windows.
The problem is that after a
first successful request to the server, the server send a FIN package to the
client and the connection is closed. When I make another r
Hi,
The problem appears to be when attempting to compile the Apache 1.3 module.
To get this working you will need to set the environment variable
APACHE_HOME to the install location of Apache 1.3.
However, based on your comments, it sounds like you want ONLY Apache 2.0
module.
Therefore you will
