orpiske opened a new pull request, #28577:
URL: https://github.com/apache/camel/pull/28577

   ## Backport of #28565
   
   Cherry-pick (`-x`) of the squash commit feb43422889f of #28565 onto 
`camel-4.22.x`.
   
   **Original PR:** #28565 - CAMEL-26347: camel-wordpress - stop adding CXF 
logging interceptors to the WordPress client
   **Original author:** @orpiske
   **Target branch:** `camel-4.22.x`
   **JIRA:** [CAMEL-26347](https://issues.apache.org/jira/browse/CAMEL-26347) 
(fix version 4.22.3)
   
   ### Changes
   
   - `AbstractWordpressServiceAdapter` no longer adds the CXF 
`LoggingInInterceptor` and `LoggingOutInterceptor` to the WordPress client, so 
requests and responses are no longer logged at `INFO` by the 
`org.apache.cxf.services` loggers
   - the unused `cxf-rt-features-logging` dependency is removed
   - the leftover log4j 1.x `log4j.properties` is removed from the main 
resources, so it is no longer shipped in the JAR
   - `WordpressServiceAdapterClientConfigurationTest` checks that an adapter's 
client has the same interceptors as a plain CXF JAX-RS client and still makes 
an authenticated call
   
   ### Difference from the original
   
   The code and the test are identical to #28565. Only the upgrade-guide note 
moved: `camel-4x-upgrade-guide-4_24.adoc` does not exist on this branch, so 
that hunk is dropped and the same text is added to 
`camel-4x-upgrade-guide-4_22.adoc` under "Upgrading from 4.22.2 to 4.22.3". The 
matching note for the 4.22 guide on `main` goes in a follow-up doc-sync PR.
   
   Verified locally with a full reactor build (`mvn clean install -DskipTests`) 
and the `camel-wordpress` tests.
   
   _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]

Reply via email to