3.19.0 release notes

docs/modules/ROOT/nav.adoc

@@ -40,6 +40,7 @@
 * xref:release-notes/index.adoc[Release notes]
 
 ifeval::[{doc-is-main} == true]
+** xref:release-notes/3.19.0.adoc[3.19.0]
 ** xref:release-notes/3.18.1.adoc[3.18.1]
 ** xref:release-notes/3.18.0.adoc[3.18.0]
 ** xref:release-notes/3.17.3.adoc[3.17.3]

docs/modules/ROOT/pages/release-notes/3.19.0.adoc

@@ -0,0 +1,67 @@
+= {quarkus-cxf-project-name} 3.19.0 release notes
+
+== Important dependency upgrades
+
+* Quarkus 3.18.x -> 3.19.0 - https://quarkus.io/blog/quarkus-3-19-0-released/[release notes]
+
+== New features
+
+=== https://github.com/quarkiverse/quarkus-cxf/issues/1680[#1680] Introduce `quarkus.cxf.client.tls-configuration-name` to set TLS options for all CXF clients
+
+Before {quarkus-cxf-project-name} 3.19.0, it was only possible to configure trust stores and key stores per CXF client via
+`xref:reference/extensions/quarkus-cxf.adoc#quarkus-cxf_quarkus-cxf-client-client-name-tls-configuration-name[quarkus.cxf.client."client-name".tls-configuration-name]`
+or (now deprecated)
+`xref:reference/extensions/quarkus-cxf.adoc#quarkus-cxf_quarkus-cxf-client-client-name-key-store[quarkus.cxf.client."client-name".key-store*]`
+and
+`xref:reference/extensions/quarkus-cxf.adoc#quarkus-cxf_quarkus-cxf-client-client-name-trust-store[quarkus.cxf.client."client-name".trust-store*]` options.
+
+The configuration might have got too verbose in case there were multiple clients.
+
+Since {quarkus-cxf-project-name} 3.19.0, it is possible to set the trust stores and key stores for all clients using the
+`xref:reference/extensions/quarkus-cxf.adoc#quarkus-cxf_quarkus-cxf-client-tls-configuration-name[quarkus.cxf.client.tls-configuration-name]` option.
+
+
+== Bugfixes
+
+=== https://github.com/quarkiverse/quarkus-cxf/issues/1697[#1697] Native build fails when using `quarkus-cxf-integration-tracing-opentelemetry` and `quarkus-jdbc-oracle`
+
+Before {quarkus-cxf-project-name} 3.19.0, combining `quarkus-jdbc-oracle` with `quarkus-cxf-integration-tracing-opentelemetry`
+or `quarkus-cxf-rt-ws-rm` in a single application resulted in an error during the build of native image as follows:
+
+[source]
+----
+org.graalvm.compiler.debug.GraalError: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException:
+Detected a MBean server in the image heap. This is currently not supported, but could be changed in the future.
+Management beans are registered in many global caches that would need to be cleared and properly re-built at image build time.
+Class of disallowed object: com.sun.jmx.mbeanserver.JmxMBeanServer
+----
+
+We have fixed this in {quarkus-cxf-project-name} 3.19.0, but note that JMX features are not supported in native mode.
+
+== Deprecations
+
+=== https://github.com/quarkiverse/quarkus-cxf/issues/1632[#1632] `io.quarkiverse.cxf:quarkus-cxf-rt-transports-http-hc5` deprecated
+
+The `io.quarkiverse.cxf:quarkus-cxf-rt-transports-http-hc5` extension is deprecated since {quarkus-cxf-project-name} 3.19.0
+and it is scheduled for removal in 3.21.0.
+Use the xref:user-guide/advanced-client-topics/asynchronous-client.adoc[asynchronous mode of `VertxHttpClientHTTPConduit`] instead.
+
+This is a part of our efforts to support only a single HTTP Conduit based on Vert.x HttpClient in the future.
+
+We deprecated the `HttpClientHTTPConduitFactory` value of
+`xref:reference/extensions/quarkus-cxf.adoc#quarkus-cxf_quarkus-cxf-http-conduit-factory[quarkus.cxf.http-conduit-factory]`
+and `xref:reference/extensions/quarkus-cxf.adoc#quarkus-cxf_quarkus-cxf-client-client-name-http-conduit-factory[quarkus.cxf.client."client-name".http-conduit-factory]`
+for the same reason in the
+xref:release-notes/3.18.0.adoc#_1633_httpclienthttpconduitfactory_value_of_http_conduit_factory_deprecated[previous release].
+
+== Documentation improvements
+
+* xref:/reference/extensions/quarkus-cxf.adoc#quarkus-cxf_quarkus-cxf-logging-limit[Document that `quarkus.cxf.logging.limit = -1` means no limit]
+* Add xref:user-guide/configuration.adoc#declarative-vs-programmatic-configuration[Declarative vs. programmatic configuration] section
+* Do not mention the deprecated `quarkus-cxf-rt-features-logging` extension in the xref:user-guide/first-soap-web-service.adoc#logging-feature[First SOAP service] guide
+* xref:user-guide/payload-logging.adoc#per-client-or-service-endpoind-payload-logging[Explain `*.logging.enabled = pretty`] and use it in examples
+* Document the xref:user-guide/advanced-client-topics/asynchronous-client.adoc[Asynchronous client] properly
+
+== Full changelog
+
+https://github.com/quarkiverse/quarkus-cxf/compare/3.18.1+++...+++3.19.0

docs/modules/ROOT/pages/release-notes/index.adoc

@@ -20,7 +20,9 @@ Those are typically released on Wednesday following the {quarkus-cxf-project-nam
 |===
 | Quarkus CXF | Release date | Quarkus Platform | CXF
 
-| xref:release-notes/3.18.1.adoc[3.18.1] | 2024-01-30 |        | 4.1.0
+| xref:release-notes/3.19.0.adoc[3.19.0] | 2024-02-24 | 3.19.0 | 4.1.0
+
+| xref:release-notes/3.18.1.adoc[3.18.1] | 2024-01-30 | 3.18.1 | 4.1.0
 | xref:release-notes/3.18.0.adoc[3.18.0] | 2024-01-23 | 3.18.0 | 4.1.0
 
 | xref:release-notes/3.17.3.adoc[3.17.3] | 2024-12-06 | 3.17.4 | 4.0.5

docs/src/test/java/io/quarkiverse/cxf/doc/it/AntoraTest.java

@@ -35,9 +35,9 @@ public void linksValid() {
 
         final Set<String> ignorables = new LinkedHashSet<>();
 
-        final ZonedDateTime deadline = ZonedDateTime.parse("2025-01-30T23:59:59+01:00[Europe/Paris]");
+        final ZonedDateTime deadline = ZonedDateTime.parse("2025-02-27T23:59:59+01:00[Europe/Paris]");
         if (ZonedDateTime.now(ZoneId.of("Europe/Paris")).isBefore(deadline)) {
-            //ignorables.add("https://quarkus.io/blog/quarkus-3-18-0-released/");
+            ignorables.add("https://quarkus.io/blog/quarkus-3-19-0-released/");
         }
 
         AntorAssured