I'm just starting to use AXIS (and web services), apart from brief acquaintances 6 and 18 months ago. I've also been working with client code, going to a no-arguments web service. I'm using AXIS at both ends and noticed the same ugly code (having to pass null) as you did, for your workaround. I tried an empty message body in the WSDL and got the no-argument method generated (using WSDL2Java, from AXIS). Unfortunately, this caused a different error to the one you're seeing. The namespace is there but the deserialization of the response has gone wrong. The same response is deserialized fine when passing null, but isn't when a no-arguments method is used.

I haven't worked out why it's gone wrong, with the no-argument method, but the response looks fine to me.

Tony

Reply via email to