This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new b27186ca4a38 CAMEL-26927: camel-wordpress - the 4.22.3 and 4.18.6
upgrade notes keep getInstance() undeprecated (#30115)
b27186ca4a38 is described below
commit b27186ca4a38356bc1a559e1190b59a326f70e38
Author: Claus Ibsen <[email protected]>
AuthorDate: Sun Nov 15 19:06:34 2026 +0100
CAMEL-26927: camel-wordpress - the 4.22.3 and 4.18.6 upgrade notes keep
getInstance() undeprecated (#30115)
Co-Authored-By: Claude Opus 5.5 <[email protected]>
---
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 7 ++++---
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 7 ++++---
2 files changed, 8 insertions(+), 6 deletions(-)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index 4a7ead7d5b72..4ee0ff879304 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -122,9 +122,10 @@ outside of it, and the producer writes through such links.
Each WordPress endpoint now has a client of its own, set up from the `url`,
`apiVersion`, `user` and `password`
options of that endpoint, and the producers and consumers of the endpoint use
that client. The endpoints no longer
-initialise the `WordpressServiceProvider.getInstance()` singleton, which is
deprecated together with its `init`
-methods. Code that read services from `WordpressServiceProvider.getInstance()`
after Camel created a WordPress endpoint
-must now use `WordpressEndpoint.getServiceProvider()`, or create a provider
with
+initialise the `WordpressServiceProvider.getInstance()` singleton; the
singleton and its `init` methods are still
+there, unchanged, for code that sets it up itself. Code that read services from
+`WordpressServiceProvider.getInstance()` after Camel created a WordPress
endpoint must now use
+`WordpressEndpoint.getServiceProvider()`, or create a provider with
`WordpressServiceProvider.create(WordpressAPIConfiguration)`.
=== camel-hazelcast - the hazelcast-seda consumer restores a transferred
exchange only with transferExchange=true
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
index 113f08962526..c8b2e6771340 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
@@ -143,9 +143,10 @@ outside of it, and the producer writes through such links.
Each WordPress endpoint now has a client of its own, set up from the `url`,
`apiVersion`, `user` and `password`
options of that endpoint, and the producers and consumers of the endpoint use
that client. The endpoints no longer
-initialise the `WordpressServiceProvider.getInstance()` singleton, which is
deprecated together with its `init`
-methods. Code that read services from `WordpressServiceProvider.getInstance()`
after Camel created a WordPress endpoint
-must now use `WordpressEndpoint.getServiceProvider()`, or create a provider
with
+initialise the `WordpressServiceProvider.getInstance()` singleton; the
singleton and its `init` methods are still
+there, unchanged, for code that sets it up itself. Code that read services from
+`WordpressServiceProvider.getInstance()` after Camel created a WordPress
endpoint must now use
+`WordpressEndpoint.getServiceProvider()`, or create a provider with
`WordpressServiceProvider.create(WordpressAPIConfiguration)`.
=== camel-hazelcast - the hazelcast-seda consumer restores a transferred
exchange only with transferExchange=true