Client using SOAP 1.2 sends no SOAP Action

[CodedNikls]

I configured my quarkus cxf client to use SOAP 1.2 via the soap-binding property like this:

quarkus.cxf.client.myClient.soap-binding=http://www.w3.org/2003/05/soap/bindings/HTTP/

The client is set up using the @CXFClient annotation and an interface generated from a wsdl file, which has been working so far.
Before, the messages it sent out used to have a Header "SOAPAction", now they don't.

Is there a solution to this I am missing or is this a bug?
Thank you in advance!

[ppalaga]

Thanks for the report @CodedNikls!

I was not able to get the SOAPAction in the request with neither the old URLConnectionHTTPConduitFactory neither with the new default VertxHttpClientHTTPConduitFactory

Could you perhaps try to change my test in such a way that it shows the "old" behavior (once you uncomment the quarkus.cxf.client.soap12.http-conduit-factory = URLConnectionHTTPConduitFactory line)?

https://github.com/quarkiverse/quarkus-cxf/pull/1644/files#diff-0f3918539c30097c2c99b110b24d1d460c20e3263a07244a54f5463a4e7b3273R126-R130

[CodedNikls]

Thank you for the answer @ppalaga! After further investigation, we have discovered that a SOAPAction header is not required in SOAP 1.2 anymore and the soap action has instead been moved to the content-type in format
"Content-Type: application/soap+xml; charset=utf-8; action="[...]""
So, right now we are stuck on the issue regarding the content-type and will need to investigate the Soap action there as well.

[ppalaga]

Thanks for the feedback, @CodedNikls. Let's focus on #1641 then.