I had the same problem. In my case the server was having a problem
serializing the object that represented the complex type.
The solution was to add a beanMapping to the deployment descriptor (wsdd)
file.
e.g. (taken from axis user guide)
<beanMapping qname="ns:local" xmlns:ns="someNamespace"
languageSpecificType="java:my.java.thingy"/>
Hope this helps
Peter
----- Original Message -----
From: "Liang, Chihong" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 14, 2002 10:40 PM
Subject: axis response is empty
> I am trying to create a web service by deploying some simple classes on
> axis.
> But the response received by my client contains no SOAP message.
>
> Let me describe the situation as below:
> Apache Axis: beta-1 rc2
> J2EE server: Tomcat 4.0 (I use the one bundled in Sun 's Web Service pack
> ea1)
> JDK: version 1.4
>
> I have tested the samples in Axis to work on the above environment.
>
> The service I created has an operation that takes a few strings and
returns
> a complex type, which is a class with three string fields. After I
published
>
> the service, I am able to use my browser to hit the endpoint with "?wsdl"
> to retrieve the generated WSDL document.
>
> Now I run my extremely simple test client, which does nothing more
> than adding parameters, setting return type, operation name and endpoint,
> using the "Call" and "Service" classes. When the client hits the service,
on
> server side
> I can see from my debugging message that the application logic behind the
> service is
> executed properly.
>
> However on the client side I got a SAXParseException, complaining that
> "Document
> root element is missing". Using tcpmon, I see that the response from axis
> contains only an HTTP header, without the SOAP message in the body (the
> request
> from the client seems to be correct).
>
> I wonder what have gone wrong. It looks like a SOAP response is not
> generated
> on server side. Is this something related to the complex data type? Any
> advise would
> be greatly appreciated.
