The second issue has been resolved now, too. The return type deserializer
was not registered with the client end, fixed this by adding extra classes
into the WSDL generation step.
-Original Message-
From: Good David [mailto:[EMAIL PROTECTED]
Sent: 07 September 2004 13:07
To: Axis-User
Su
Hi David,
I have had this issue previously. Firstly, the complex type in the schema is
where you set this up but there is a SERIOUS issue with the naming.
The Schema spec does not allow a $ character in a qname (it is not in the
allowable range of legal characters). Axis does however ignore thi
