Skip to content

fix(sitemanage): drop non-existent verbose property on CXF LoggingFeature bean #204

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
natechadwick merged 1 commit into from
Sep 8, 2026
Merged

fix(sitemanage): drop non-existent verbose property on CXF LoggingFeature bean #204

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions ...ks/PR#-DependencyVulnerabilityAnalysis/issues/168-t2-3-cxf-logging-hardening.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,19 @@ The default `<cxf:logging/>` in CXF 3.5.x:
- uses multi-line pretty-printed format (slow, large)

The new `cxfLoggingFeature` bean is configured with safe defaults:
- `verbose=false` — log only the first line of each message (method + URL + status), not the payload
- `limit=4096` — cap logged payload at 4 KB
- `limit=4096` — cap the logged payload at 4 KB (this is what does the actual safety work in 3.5.x; the interceptor writes a single-line summary once the limit is reached and truncates the rest)
- `prettyLogging=false` — single-line format (faster, smaller)

> **CXF 3.5.x note:** `LoggingFeature` no longer exposes a `verbose` setter in 3.5.x
> (it was removed when the inner `LoggingFeature$Portable` class was introduced; the
> public API is now `setLimit(int)` and `setPrettyLogging(boolean)` plus the
> `LoggingFeature(String, String, int, boolean, boolean)` constructor for `inLocation`,
> `outLocation`, `limit`, `prettyLogging`, and `showBinary`). The earlier revision of
> this doc and the original bean both set `<property name="verbose" .../>`, which
> makes Spring throw `NotWritablePropertyException` at startup and prevents the
> Rhythmyx webapp from starting. The bean has been corrected to use only the
> properties that 3.5.11 actually supports.

### Scope

This applies to the **sitemanage-jax-rs** server only. The other `<jaxrs:server>` blocks in the file don't have `<cxf:logging/>` and are unaffected. The 5 delivery-tier-suite webapps use Jersey (not CXF) and are out of scope for this PR (separate workstream).
Expand Down
1 change: 0 additions & 1 deletion .../server/rx/deploy/rxapp.ear/rxapp.war/WEB-INF/config/spring/projects/sitemanage-beans.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1865,7 +1865,6 @@ http://cxf.apache.org/schemas/jaxrs.xsd">
(method + URL + status) and caps the payload at 4 KB.
-->
<bean id="cxfLoggingFeature" class="org.apache.cxf.feature.LoggingFeature">
<property name="verbose" value="false"/>
<property name="limit" value="4096"/>
<property name="prettyLogging" value="false"/>
</bean>
Expand Down
Loading