[SWS-828] Setting bspCompliant = false has effect only for first request Created: 10/Apr/13  Updated: 12/Apr/13  Resolved: 12/Apr/13

Status: Resolved
Project: Spring Web Services
Component/s: None
Affects Version/s: 2.1.2
Fix Version/s: 2.1.3

Type: Bug Priority: Major
Reporter: Juergen Ebert Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


Symptom: Setting the property 'bspCompliant' on Wss4jSecurityInterceptor to false has an effect only for the first web service request after application start. Setting 'wsiBspCompliant=false' on the wssConfig object has the same result.

Cause: WSS4J sets back the value in WssConfig to true in each WSHandler.doSenderAction() call. WSHandler.doSenderAction() asks the Spring Wss4JHandler for the value of the configuration option IS_BSP_COMPLIANT in the set of options, and Wss4JHandler returns null. The default behaviour of WSS4J is: If an option is not set in the handler, the value defaults to true.

Possible correction: add IS_BSP_COMPLIANT to the set of options in Wss4JHandler on call to Wss4jSecurityInterceptor.setBspCompliant().

Generated at Tue Oct 23 11:35:11 UTC 2018 using JIRA 7.9.2#79002-sha1:3bb15b68ecd99a30eb364c4c1a393359bcad6278.