Open KoenigsKind opened 6 months ago
We have troubles with the Content-Type header generated by JAX-WS-RT, it differs slightly from the Content-Type we get, when we execute the same request in SoapUI.
This is the header which is created by JAX-WS:
Content-Type: multipart/related;[...]start-info="applicaton/soap+xml;action=\"http://foo.bar\"";
While the expected header would look like the following:
Content-Type: multipart/related;[...]start-info="applicaton/soap+xml";action="http://foo.bar";
Is there a reason the action is embedded inside the start-info parameter?
The problematic code can be found in MtomCodec.java at lines 120 and 133.
We have troubles with the Content-Type header generated by JAX-WS-RT, it differs slightly from the Content-Type we get, when we execute the same request in SoapUI.
This is the header which is created by JAX-WS:
While the expected header would look like the following:
Is there a reason the action is embedded inside the start-info parameter?
The problematic code can be found in MtomCodec.java at lines 120 and 133.