axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kevinlampert <kevin.lamp...@beaconps.net>
Subject Re: org.apache.axis2.AxisFault: SOAP header missing
Date Wed, 04 Mar 2009 22:48:28 GMT

I solved my problem.

I removed the <sp:IncludeTimestamp/> from the policy.xml. Apparently, this
inclusion causes the client to look for a security header in the server
response. Once I removed it, the client retrieved my data just fine.





kevinlampert wrote:
> 
> I am writing a java client to consume a web service that I have no control
> of. The web service requires a username and password for authentication.
> I have configured Rampart to place the data in the security header and can
> capture the request being sent and see the correct header information. I
> have the callback handler working correctly.
> 
> If I submit just the SOAP message (I captured using tcpmon) using XMLSpy,
> the message works correctly and the response from the web service appears
> correct.
> 
> My java client, however, throws an exception:
> 
> Exception: org.apache.axis2.AxisFault: SOAP header missing
> org.apache.axis2.AxisFault: SOAP header missing
>         at
> org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFa
> ult(RampartReceiver.java:166)
>         at
> org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.jav
> a:99)
>         at org.apache.axis2.engine.Phase.invoke(Phase.java:317)
>         at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
>         at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)
>         at
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(
> OutInAxisOperation.java:363)
>         at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisO
> peration.java:416)
>         at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(Out
> InAxisOperation.java:228)
> 
> My question is:
> Is there something to tell Rampart that the security header is ONLY
> required for client outbound messages and that inbound messages to client
> WILL NOT have a security header?
> 
> Other ideas, or something I am missing?
> I can add any additional information you may require.
> 
> Thanks!
> 

-- 
View this message in context: http://www.nabble.com/org.apache.axis2.AxisFault%3A-SOAP-header-missing-tp22315041p22341342.html
Sent from the Axis - User mailing list archive at Nabble.com.


Mime
View raw message