You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Aurélien Pupier (Jira)" <ji...@apache.org> on 2021/02/01 10:16:00 UTC

[jira] [Comment Edited] (CAMEL-16116) False positive validation forsome special SpringBoot properties

    [ https://issues.apache.org/jira/browse/CAMEL-16116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276226#comment-17276226 ] 

Aurélien Pupier edited comment on CAMEL-16116 at 2/1/21, 10:15 AM:
-------------------------------------------------------------------

{quote}This is only for validating camel options, not special spring boot options.{quote}

how to make the difference between a Camel option and a springboot option?


i think this is a bug. There is also a false-positive with camel-report-maven-plugin:

{noformat}
[WARNING] Configuration validation error at: (application.properties:21)

	camel.component.servlet.mapping.context-path=/example/*

	                                context-path    Unknown option


[WARNING] Configuration validation error: (0 = passed, 1 = invalid, 0 = incapable, 0 = unknown components, 0 = deprecated options)
{noformat}

As first iteration, a fix for the bug would be to ignore "springboot properties" (if there is a way to detect it).
As second iteration, an enhancement to validate also the springboot properties would be nice.


was (Author: apupier):
"This is only for validating camel options, not special spring boot options."

how to make the difference between a Camel option and a springboot option?


i think this is a bug. There is also a false-positive with camel-report-maven-plugin:

{noformat}
[WARNING] Configuration validation error at: (application.properties:21)

	camel.component.servlet.mapping.context-path=/example/*

	                                context-path    Unknown option


[WARNING] Configuration validation error: (0 = passed, 1 = invalid, 0 = incapable, 0 = unknown components, 0 = deprecated options)
{noformat}

As first iteration, a fix for the bug would be to ignore "springboot properties" (if there is a way to detect it).
As second iteration, an enhancement to validate also the springboot properties would be nice.

> False positive validation forsome special SpringBoot properties
> ---------------------------------------------------------------
>
>                 Key: CAMEL-16116
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16116
>             Project: Camel
>          Issue Type: New Feature
>          Components: tooling
>    Affects Versions: 3.7.1
>            Reporter: Aurélien Pupier
>            Priority: Minor
>             Fix For: 3.x
>
>
> https://camel.apache.org/components/latest/servlet-component.html#_usage_with_spring_boot
> calling  org.apache.camel.catalog.CamelCatalog.validateConfigurationProperty("camel.component.servlet.mapping.context-path")
> there is the same result  with and without sertting the SpringBootRuntimeProvider on the catalog



--
This message was sent by Atlassian Jira
(v8.3.4#803005)