ConfigJSR
ConfigJSR copied to clipboard
eclipse
JSR382
The `ConfigProviderResolver` should not initialize on just being imported for a variety of reasons. The major reasons is makes initialization less predictable and bootstrapping more complicated. Performance is also a...
The spec leads @Emily-Jiang and @struberg decided to withdraw this specification from the JCP and continue the work under the JakartaEE umbrella. This means we will rename all packages to...
In Apache DeltaSpike you can define an interface which gets automatically provided as accessor for configured values http://deltaspike.apache.org/documentation/configuration.html#_interface_based_configuration It's basically the approach first seen in Owner. You simply write an...
Currently we only support injecting a `@ConfigProperty Provider` but this has some issues on Weld. So we might think about additionally also supporting injection of `Supplier `
Based on https://github.com/eclipse/ConfigJSR/issues/26 I had a look at the `spec` and saw that we currently define the default config properties file as `META-INF/javaconfig.properties`. Actually I'm not really happy with the...
Should we introduce a ProjectStage in JSR-382?
In sensitive environments I would like to know the source of each configuration entry. Configuration can change the behaviour of an whole application, so the final source of an entry...
It would be a very helpful feature -- not only for container / orchestration environments -- to trigger updates in ConfigSources that originate from properties files, when these files are...