Please support CXF Consumers with Camel-on-EAP / Wildfly-Camel

As noted in the Wildfly-Camel doc:
"IMPORTANT: At present the WildFly Camel Subsytem does not support CXF consumers. E.g endpoints defined as from("cxf://..."). Although, it is possible to mimic CXF consumer behaviour using the CamelProxy."

This is an inconvenience to our customers, who have easier use of web service consumers through JEE/Jax-WS, Camel (using a CXF consumer) and even the old SOA-P toolkit. It is a step backward for our users to construct a consumer with Camel-on-EAP or SwitchYard. (SwitchYard makes the user provide a 'transformer' that manages the data marshalling.)

Please make it easier for a user to offer a SOAP contract with Camel-on-EAP.