[
https://issues.apache.org/jira/browse/CAMEL-14311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999015#comment-16999015
]
Aurélien Pupier edited comment on CAMEL-14311 at 12/18/19 10:17 AM:
--------------------------------------------------------------------
In the catalog there is the notion of Runtimeprovider. Maybe we can rely on
that.
for instance, if I have
camel.component.timer.aninvalidoption=1000
it will report an error saying that the "aninvalidoption" is an unknown
property.
if I have
camel.component.timer.basicPropertyBinding=toto
it will report an error saying that the value must be a boolean .
Even if we canot enforce it, I think we can expect that people using
camel.{component|main|rest|hystrix|resilience4j}.* are using Camel
was (Author: apupier):
In the catalog there is the notion of Runtimeprovider. Maybe we can rely on
that.
for instance, if I have
camel.component.timer.aninvalidoption=1000
it will report an error saying that the "invalidoption" is an unknown property.
if I have
camel.component.timer.basicPropertyBinding=toto
it will report an error saying that the value must be a boolean .
Even if we canot enforce it, I think we can expect that people using
camel.{component|main|rest|hystrix|resilience4j}.* are using Camel
> Provide validation for Camel properties files
> ---------------------------------------------
>
> Key: CAMEL-14311
> URL: https://issues.apache.org/jira/browse/CAMEL-14311
> Project: Camel
> Issue Type: Improvement
> Components: camel-main, tooling
> Affects Versions: 3.0.0
> Reporter: Aurélien Pupier
> Priority: Major
>
> it would be nice to have validation of Camel Properties files as we have for
> Camel URIs on other types of Camel files.
> Having methods like CamelCatalog.validatePropertiesFile(String) and/or
> CamelCatalog.validatePropertyEntry(String)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
