[SWS-416] Wss4jSecurityInterceptor loosing SOAPAction header Created: 15/Aug/08 Updated: 04/May/12 Resolved: 28/Aug/08 |
|
Status: | Closed |
Project: | Spring Web Services |
Component/s: | Security |
Affects Version/s: | 1.5.3 |
Fix Version/s: | 1.5.5 |
Type: | Bug | Priority: | Major |
Reporter: | Martin Bosak | Assignee: | Arjen Poutsma |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() |
Description |
When the Wss4jSecurityInterceptor replaces the AxiomMessage in the SoapMessage, if the original SoapMessage already had a SoapAction set, the value is lost. I believe, in the Wss4jSecurityInterceptor.replaceMessage() method, the following workaround should be done: // replace the Axiom message axiomMessage.setAxiomMessage(newMessage); soapMessage.setSoapAction(tempSoapAction); |
Comments |
Comment by Tareq Abedrabbo [ 28/Aug/08 ] |
patch + unit test. |
Comment by Arjen Poutsma [ 28/Aug/08 ] |
Fixed. Thanks! |
Comment by Arjen Poutsma [ 04/May/12 ] |
Closing old issues |