I’ve been working on porting the website table generation changes I made for components in latest and 3.2.x to 2.x and have run into something I haven’t been able to understand or figure out.
For some reason that I don’t understand, I started getting this change in generated documentation: git diff components/camel-spring/src/main/docs/spring-event-component.adoc diff --git a/components/camel-spring/src/main/docs/spring-event-component.adoc b/components/camel-spring/src/main/docs/spring-event-component.adoc index f8b8cc7acc7..4f046c24f73 100644 --- a/components/camel-spring/src/main/docs/spring-event-component.adoc +++ b/components/camel-spring/src/main/docs/spring-event-component.adoc @@ -85,7 +85,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s ---- -The component supports 4 options, which are listed below. +The component supports 2 options, which are listed below. @@ -94,7 +94,5 @@ The component supports 4 options, which are listed below. | Name | Description | Default | Type | *camel.component.spring-event.enabled* | Enable spring-event component | true | Boolean | *camel.component.spring-event.resolve-property-placeholders* | Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. | true | Boolean -| *camel.language.spel.enabled* | Enable spel language | true | Boolean -| *camel.language.spel.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean |=== // spring-boot-auto-configure options: END These (removed) options are still present in latest. Are they actually part of the spring-event-component spring boot configuration? The trim method appears on the spel language class. If these are correctly exposed in spring boot in the event component, what connects the event component to the spel language class/configuration? Thanks, David Jencks
