axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Bell <>
Subject Re: AxisFault produces empty http 202
Date Mon, 30 Jul 2007 08:42:11 GMT
Hi Deepal.

Deepal jayasinghe schrieb:

> I create a POJO and deploy and I got the expected result , so will you
> be able to provide me more data to re-generate the issues. FYI I have
> attached my POJO.

I attached two WSDL files (stupid SQL wrapper plus common types and 
messages). The file with suffix orig is the web service which I want to 
implement. The file with the short filename is the specification which 
works. It looks like that AxisFault will only be correctly handled by 
the InOut message receiver. The RobustInOnly message receiver has a 
problem. Perhaps this has something to do with the initialization of the 
web server or the inheritaed classes.

BTW some details about my server implementation. I always generate the 
skeleton and the interface. My implementation class extends the 
skeleton. If I throw the custom exception (specified in the WSDL)in my 
implementation then his exception will be catched by the generated 
message receiver. This receiver packs the exception into an AxisFault 
and throw it again. The problem is that it looks like the handling of 
the RobustInOnly and InOut message receivers is different.

If you have a normal InOut receiver then you get an http 202 code plus 
the SOAP error. If you have RobustInOnly then you get only http 202.

Best regards


Michael Bell                    Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482       ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704       Unter den Linden 6   D-10099 Berlin

X.509 CA Certificates / Wurzelzertifikate

View raw message