The cxf java2wsdl seems to fail in generating the wsdl portType/operation element in some cases where soapHeader and IN/OUT parameters are used at the same time. This was revealed by the webparam3 reverse test configuration in the jws tck5 module.
In that case we have

<wsdl:portType name="webParam3WebService">
<wsdl:operation name="hello3">
<wsdl:input name="hello3" message="tns:hello3">
</wsdl:input>
...

instead of

<wsdl:portType name="webParam3WebService">
<wsdl:operation name="hello3" parameterOrder="id Name Employee">
<wsdl:input name="hello3" message="tns:hello3">
</wsdl:input>
...

We should first reproduce this in a test case in our testsuite, then understand if this is actually a cxf issue or an integration one.