[
https://issues.apache.org/jira/browse/CAMEL-25434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-25434.
---------------------------------
Fix Version/s: 4.23.0
Resolution: Fixed
Fixed by https://github.com/apache/camel/pull/27534. The runtime did record the
location; camel get properties dropped any location it had no readable name
for, such as a properties file. The camel-jbang monitor's Configuration tab now
also shows the location when a property has no resolved source.
> camel-jbang - camel run does not record where a property comes from, so camel
> get properties shows no location
> --------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-25434
> URL: https://issues.apache.org/jira/browse/CAMEL-25434
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 4.23.0
>
>
> In an integration run with camel run (JBang), the properties dev console has
> no source or location for the properties loaded from application.properties:
> camel get properties shows an empty LOCATION column, and the camel-jbang
> monitor's Configuration tab an empty SOURCE column, on every row.
> Reproduce: camel run routes.camel.yaml beans.yaml Greeter.java
> application.properties (quick-start/routes of camel-jbang-examples), then
> camel get properties:
> {noformat}
> PID NAME LOCATION KEY VALUE
> 2707 props-test greeter.gree… Hello
> 2707 props-test greeter.peri… 1000
> {noformat}
> Expected: the location of each value (application.properties, a profile file,
> the command line with --prop, an environment variable, a default), as the
> console reports for a value whose source is known. The properties are likely
> loaded into the initial properties of camel-main without a location, so the
> properties lookup listener has none to record.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
