Reference
Quarkus CXF
Here is the list of extensions produced by this project. Please follow the links under the extension names to learn about how to use them, about their configuration and about any known limitations.
| Quarkus CXF extension | Support level | Since | Supported standards |
|---|---|---|---|
Quarkus CXF |
Stable |
0.1.0 |
|
Quarkus CXF Metrics Feature |
Stable |
0.14.0 |
|
Quarkus CXF OpenTelemetry |
Stable |
2.7.0 |
|
Quarkus CXF WS-Security |
Stable |
0.14.0 |
|
Quarkus CXF WS-ReliableMessaging |
Stable |
1.5.3 |
|
Quarkus CXF Security Token Service (STS) |
Stable |
1.5.3 |
|
Quarkus CXF HTTP Async Transport |
Stable |
1.1.0 |
|
Quarkus CXF XJC Plugins |
Stable |
1.5.11 |
Supported CXF modules
Here is a list of CXF modules supported by Quarkus CXF. You should typically not depend on these directly, but rather use some of the extensions listed above that brings the given CXF module as a transitive dependency.
Front ends
Out of CXF front ends only the
JAX-WS front end is fully supported by quarkus-cxf.
The Simple front end may work in JVM mode, but it is not tested properly. We advise not to use it.
Data Bindings
Out of CXF Data Bindings only the following ones are supported:
Transports
Out of CXF Transports only the following ones are supported:
-
quarkus-cxfimplements its own custom transport based on Quarkus and Vert.x for serving SOAP endpoints -
HTTP client via
quarkus-cxf, including -
Asynchronous Client HTTP Transport via
quarkus-cxf-rt-transports-http-hc5
Tools
-
wsdl2Java- see the Generate the Model classes from WSDL section of User guide -
java2ws- see the Generate WSDL from Java section of User guide
Supported SOAP Bindings
All CXF WSDL Bindings are supported.
In order to switch to SOAP 1.2 or to add MTOM, set quarkus.cxf.[client|endpoint]."name".soap-binding to one of the following values:
| Binding | Property Value |
|---|---|
SOAP 1.1 (default) |
|
SOAP 1.2 |
|
SOAP 1.1 with MTOM |
|
SOAP 1.2 with MTOM |
Unsupported CXF modules
Here is a list of CXF modules currently not supported by Quarkus CXF along with possible alternatives and/or reasons why the given module is not supported.
| CXF module | Alternative |
|---|---|
JAX-RS |
|
Use JAXB and JAX-WS |
|
DOSGI |
|
JiBX |
Use JAXB and JAX-WS |
Local transport |
Use HTTP transport |
JMS transport |
Use HTTP transport |
JBI |
Deprecated in CXF use HTTP transport |
UDP transport |
Use HTTP transport |
Use HTTP transport |
|
WebSocket transport |
Use HTTP transport |
Clustering |
|
CORBA
|
Use JAX-WS |
SDO databinding |
|
Deprecated in CXF |
|
Use JAX-WS |
|
Use HTTP transport |
|
WS-Transfer runtime |
|
Throttling |
Use load balancer |
Supported CXF annotations
Here is the status of CXF annotations on Quarkus.
Unless stated otherwise, the support is available via io.quarkiverse.cxf:quarkus-cxf.
| Annotation | Status |
|---|---|
|
Supported |
|
Supported |
|
Supported |
|
Supported |
|
Supported |
|
Supported |
|
Supported |
|
Supported |
|
Only the default value |
|
Supported |
|
Supported |
|
Supported via |
|
Supported |
|
Supported |
|
Supported |
|
Supported |
|
Supported |