You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-user@axis.apache.org by Håkon Sagehaug <Ha...@bccs.uib.no> on 2009/04/24 13:21:50 UTC

Problems with no soap header, when a fault it thrown from a ws with rampart enabled, client side

Hi

I had the same problem as described here [1], and followed the solution and
it worked out fine. I call the service from java code generated with axis2
tool wsdl2java. So now the problem, it seems that my client expects a SOAP
header to be in the response message, but when a fault is thrown there is no
header included I get

org.apache.axis2.AxisFault: SOAP header missing

message at the client. I tested the ws in soapui and the service is throwing
the exception as it should.
Does anyone have a solution for this? Should there be a soap header when a
soap fault is the response message?

[1]
http://mail-archives.apache.org/mod_mbox/ws-rampart-dev/200901.mbox/%3C9e2fff830901070853j45316ff9u62af768475a79b94@mail.gmail.com%3E

-- 
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)