oscerd opened a new pull request, #1908: URL: https://github.com/apache/camel-spring-boot/pull/1908
Cherry-pick of #1898 onto `camel-spring-boot-4.22.x`. **Original PR:** #1898 — CAMEL-24499: camel-spring-boot - route detail view bypasses the route.start.exception serialization filter **JIRA:** [CAMEL-24499](https://issues.apache.org/jira/browse/CAMEL-24499) ### What it fixes `RouteEndpointInfo` annotates its properties map with `@JsonIgnoreProperties({"route.start.exception"})`, but `RouteDetailsEndpointInfo` re-declared the same field without the annotation plus a `getProperties()` override, so the actuator detail operation serialized the property the base view filters. That property holds the `Throwable` itself, so Jackson emitted the whole object graph — nested causes, every stack frame with class, file and line, classloader names and the JDK version. Both the annotation and the shadowing field were introduced together under CAMEL-20993, so the filter was intended and the subclass field simply escaped it. **The defect is present on this branch** — verified before cherry-picking: `CamelRoutesEndpoint` here has two `private final Map<String, Object> properties` declarations (base + shadow); after the pick it has one. ### Not a public API change `RouteDetailsEndpointInfo.getProperties()` was an override of a method the public base class `RouteEndpointInfo` also declares, so it stays available on the subclass by inheritance — source and binary compatible. ### Verification on this branch - Cherry-pick applied cleanly - `CamelRoutesEndpointStartExceptionTest` — 2/2 pass - Full reactor `mvn clean install -DskipTests` — BUILD SUCCESS (447 modules) - Awaitility is available in test scope here, so the test's asynchronous precondition works as on main Scope is two files: the endpoint class and its new regression test. No behaviour change beyond removing the leak. -- 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]
