Hi Stephanos,
Unfortunately, it's really on the service provider to fix their broken
implementation. You can of course get your client to work by patching the
Axis2 code (it is open source after all :)) to remove the checks, but that
would be sort of like patching a TCP stack to ignore window siz
I'm trying to consume a web service using Axis2 1.4.1 and Rampart 1.4.
The service requires WS-Security in the form of a signed request (no
encryption), using x.509 tokens.
I generated the client code from a WSDL file provided by the service.
Unfortunately, it did not contain any security anotat
Unsubscribe
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Hi,
I have a web service class as shown below.
import org.w3c.dom.Document;
public class EchoXml {
public Document echo(Document xml) {
return xml;
}
}
*I will not be able to modify this class by using OMElement instead of
Document. I have to use the class in this format o
Additional note. The http response header says:
...
Server Apache
X-AspNet-Version2.0.50727
Hence I am facing a
apache -> mono-server
or
mod_mono (which is said to support http/1.1 ...)
setup
-Ursprüngliche Nachricht-
Von: Clemens Wyss [mailto:[email protected]
Hi all,
I am trying to talk to .NET Webservice. Unfortunately I get the above mentioned
error message:
org.apache.axis2.AxisFault: Could not deserialize Soap message
UNLESS I force my client/stub to http/1.0
(setProperty(HTTPConstants.HTTP_PROTOCOL_VERSION,
HTTPConstants.HEADER_PROTOCOL_10)
