Quarkus CXF 2.6.0 release notes

Important dependency upgrades:

New and noteworthy in Quarkus CXF

Logging extension is deprecated

The Logging functionality and all associated configuration options were moved to io.quarkiverse.cxf:quarkus-cxf extension. The io.quarkiverse.cxf:quarkus-cxf-rt-features-logging extension is now deprecated and you can remove it from your projects. It will be removed altogether in the future.

quarkus.cxf.http-conduit-factory fixed

See #1047

Configurable destination folder of wsdl2java

The directory where the wsdl2java embedded in quarkus-cxf extension produces the Java classes is now configurable via the quarkus.cxf.codegen.wsdl2java.output-directory property.

Possible thread leaks with CXF clients using java.net.http.HttpClient

This issue was originally reported as CXF-8885.

CXF client proxies implement java.io.Closeable. Therefore, it is important to call ((Closeable) proxy).close() once the client is not needed anymore to free all associated system resources, such as threads.

Quarkus CXF now takes care for closing the clients injected via @io.quarkiverse.cxf.annotation.CXFClient automatically as soon as they are disposed by the CDI container.

For client proxies created manually, it is up to you to call ((Closeable) proxy).close().

For more information, see Prevent resource leaks section of the user guide.

Large responses not written slowly anymore

Before Quarkus CXF 2.6.0, large responses were written slowly due to allocating too small buffers. This issue is now fixed.

More WS-Security configuration options covered by tests

We are continually improving the test coverage of the WS-Security configuration options. There is now less options marked with the warning

This option is experimental, because it is not covered by tests yet.

Documentation improvements