Ubuntu
axis2c package

Incorrect SOAP fault handling when Rampart is engaged

Bug #431251 reported by k0ekk0ek on 2009-09-17

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	axis2c (Ubuntu)	New	Undecided	Unassigned

Bug Description

I'm using WSO2 WSF/PHP and I compiled it against this package. I found a bug when using Rampart/C and throwing a WSFault. Another person, François Mireaux, also encountered this bug, he created a patch and send it upstream. Below is his description.

[quote]
When axis2_msg_recv_receive_impl detects that response is a SOAP fault, it doesn't send this response but delegates sending to HTTP transport (http_transport_utils.c). But the fault message context created by axis2_engine_create_fault_msg_ctx doesn't copy the base axis2 context contained in input message context, as in axis2_core_utils_create_out_msg_ctx used in normal processing. So Rampart context is not found, Rampart fails to process and SOAP fault is send without security headers.
[/quote]

For extra information, please see https://issues.apache.org/jira/browse/AXIS2C-1394. I've attached the patch I used.