Hi all,
Well, I fixed the problem, by enabling the java.net debug mode, I could
easily track down the problem and solve it (reading between the lines of
encoded and decoded stuff). Yesterday I ended up with the XML message as
I've sended it, without knowing it I was nearly finished. I only had to
specify the return type (because it is an array-agr), and voila.
Note that I'm not unhappy with Axis, actually I'm quite happy with it. I
hope the things I say help improving Axis. Like the suggestion to return the
plain HTTP-output when the response serialiser doesn't receive anything it
can parse (for example when you are talking to a Microsoft webservice which
doesn't use SOAP:FAULT to say things back but only in plain text without any
soap headers).
I hope Axis2 will end up as good as Axis1. For example, it's a good thing to
use a deploy mechanism that looks more like Tomcat. I wondered why you'ld
want to introduce another deploy language (the one in Apache SOAP and now
the one in Apache Axis1) when already having the services.xml mechanism in
Tomcat.
Thanks for now,
Niels Gorisse
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.com/
