Closed vavishal closed 6 years ago
After upgrading from 12.1.1 to 12.2.1.3, the customer has issues with his WS-A enabled web service because the soap reply contains duplicated WSA:Action/MessageID/To headers and the client rejected it. The SOAP request had these WS-A headers:
http://facade.ws.tecs.pax/PersonIntegrationAsyncWS/alarm_v1Request/wsa:Action 9b0608b4-cf80-47b9-bde6-38229c9cd41d/wsa:MessageID http://facade.ws.tecs.pax/PersonIntegrationAsyncWS/alarm_v1Request/wsa:To wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address wsa:ReferenceParameters wsa:Actionhttp://facade.ws.tecs.pax/PersonIntegrationAsyncWS/alarm_v1Request/wsa:Action wsa:MessageIDe51373fd-0656-4f8d-949f-b8053339418e/wsa:MessageID wsa:Tohttp://facade.ws.tecs.pax/PersonIntegrationAsyncWS/alarm_v1Request/wsa:To
Changed the jaxws-ri code from add to addOrReplace method to avoid duplicates
Updated the copyright year
After upgrading from 12.1.1 to 12.2.1.3, the customer has issues with his WS-A enabled web service because the soap reply contains duplicated WSA:Action/MessageID/To headers and the client rejected it. The SOAP request had these WS-A headers:
Changed the jaxws-ri code from add to addOrReplace method to avoid duplicates