orpiske opened a new pull request, #28579: URL: https://github.com/apache/camel/pull/28579
## Backport of #28565 Cherry-pick of feb43422889f21ff4959c3766b87ee1305f52687 (#28565) onto `camel-4.18.x`. **Original PR:** #28565 - CAMEL-26347: camel-wordpress - stop adding CXF logging interceptors to the WordPress client **Original author:** @orpiske **Target branch:** `camel-4.18.x` ### Conflict resolution The `camel-4x-upgrade-guide-4_24.adoc` hunk is dropped: that file does not exist on `camel-4.18.x` (modify/delete conflict). As `AGENTS.md` asks for backported changes, the 4.18.6 upgrade guide entry is added on `main` instead, in a separate PR. The code and test changes are identical to #28565. ### Original description The camel-wordpress service adapters added the CXF `LoggingInInterceptor` and `LoggingOutInterceptor` to every WordPress client they created. Because of that, every request and response the component exchanged with the WordPress server was logged at `INFO` level by the `org.apache.cxf.services` loggers, with no way to turn it off from the endpoint. This PR: - removes the two interceptors from `AbstractWordpressServiceAdapter`, so the client keeps the interceptors CXF sets up for a JAX-RS client - removes the `cxf-rt-features-logging` dependency, which is no longer used - removes the leftover log4j 1.x `src/main/resources/log4j.properties` from the main resources, so it is no longer shipped in the `camel-wordpress` JAR - adds `WordpressServiceAdapterClientConfigurationTest`, which checks that an adapter's client has the same interceptors as a plain CXF JAX-RS client and still makes an authenticated call ### Validation - Full reactor `mvn clean install -DskipTests` (JDK 21) - `mvn verify` in `components/camel-wordpress`: 21 tests, 0 failures _Claude Code on behalf of orpiske_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
