Skip to content

Fix named route configurations not inherited by kamelets#21437

Merged
davsclaus merged 1 commit intoapache:mainfrom
bartoszpop:fix-route-conf-not-inherited
Feb 13, 2026
Merged

Fix named route configurations not inherited by kamelets#21437
davsclaus merged 1 commit intoapache:mainfrom
bartoszpop:fix-route-conf-not-inherited

Conversation

@bartoszpop
Copy link
Contributor

Description

After changes introduced in scope of CAMEL-21599, kamelets inherit the error handler from the parent route. However, if the parent route has a route configuration with an error handler or an onException block, it won't be inherited.

Target

  • I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

  • If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

  • I checked that each commit in the pull request has a meaningful subject line and body.
  • I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

After changes introduced in scope of CAMEL-21599, kamelets inherit the error handler from the parent route. However, if the parent route has a route configuration with an error handler or an onException block, it won't be inherited.
@bartoszpop bartoszpop force-pushed the fix-route-conf-not-inherited branch from 7761894 to 591ee49 Compare February 13, 2026 02:35
@davsclaus
Copy link
Contributor

https://issues.apache.org/jira/browse/CAMEL-22998

@davsclaus davsclaus merged commit 3864e8d into apache:main Feb 13, 2026
3 checks passed
davsclaus pushed a commit that referenced this pull request Feb 13, 2026
#21437)

CAMEL-22998: After changes introduced in scope of CAMEL-21599, kamelets inherit the error handler from the parent route. However, if the parent route has a route configuration with an error handler or an onException block, it won't be inherited.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants