> From: Aleksander Slominski [mailto:[EMAIL PROTECTED]
[...]
> what i would do: write a small test program and see how long does it
> take for the XML parser you use to parse this ~120 KB SOAP reply (N),
> how long does it take to write XML for SOAP request (is it small?) (M),
> and then compare
Thanks Yuval for your suggestion to use JProfiler.
I ran my test in it, an although I don't have a lot of experience
using profilers, I believe I've found that only about 25% of the
time used was network overhead, and about 70% was XML processing.
This means that the axis client uses about 650 ms
Hi. My axis client (1.1) is spending more time than I excpected
it to receiving and parsing a reply from my axis server. How can
I measure where the time is used? (the ouput from -Xrunhprof was not
wery helpful here). Measuring parsing time will be sufficient.
--
Regards
André Risnes
Replying to myself now... Well i figured it out, sort of. My IDE,
in which i ran the test that failed, used a different output folder
for class files than my build script. Somehow this caused a mismatch
somewhere. They now use the same folder, and it works.
--
Regards
André Risnes
Hi. I have a bunch of enum classes with custom serializers and deserializers.
One of these classes is called AccountCategory. When my SOAP client tries to
deserialize an instance of this class returned from my server, i get the
following exception:
AxisFault
faultCode: {http://schemas.xmlsoap.org
