Hi,
i have the same problem, this happens because apche soap is not strictly
compliant with some namespace attribtues,
you have to map the response, in your deploy file you must add a line like
this
http://schemas.xmlsoap.org/soap/encoding/";
xmlns:x="" qname="x:result"
xml2JavaClassNa
Hello,
We are experiencing a problem using RPC; (Apache SOAP 2.2 + tomcat 4.01 +
10Mbit ethernet LAN).
When client and service are running on the same PC, a simple RPC call takes
about 25 msec for the roundtrip.
On the LAN the same RPC call takes about 250 msec !!!
Strangly, both CPUs are bar
hi there,
the GLUE web services platform gets about 700 messages/second
on a standard PC. (http://www.themindelectric.com)
a lot depends on whether the web services platform makes
use of HTTP 1.1. persistent connections and how fast its XML
parser is.
HTTP is actually pretty efficient and not t
Hello,
Please unsubscribe me.
Cesar.
> -Original Message-
> From: Derik Crouch [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 17, 2002 10:42 PM
> To: [EMAIL PROTECTED]
> Subject: Problem with response from MS Soap
>
>
> Hello,
>
> I'm currently building a Java client that will be using
> Apache Soap API
> to commu
unsubscrible me
unsubscrible me
Just yesterday I have tried Tomcat 3.2.3 as http transport plug-in for Wasp
and realized that it is very slow (more than 10 times slower than standalone
Wasp).
Radovan
Radovan Janecek
VP, Engineering, Systinet (formerly Idoox)
http://www.systinet.com
- Original Message -
From: "Herre
When calling a MS Soap Server you need to explicitly map the return turn
types...use this snippet of code...if that doesn't work then I think you
have another older parser in the path somewhere that is causing your
problems...**Note you must do this BEFORE you invoke the call...
//ADD YOUR OWN
