Mark Struberg

We should probably rename it to something else? `@Configured` for example?

The whole point of Config is that the application (the user code) does _not_ need to know where the configured value is coming from. I fear this will also add...

> all apps with higher sensitivity. Core banking, medical systems, machine control.... Sorry no, that's simply not true from my experience in working in all those fields! An application might...

@tomas-langer can you take over? txs!

I think this is not a core functionality of the ConfigJSR itself. It is perfectly possible to register a custon `ConfigSource` which can do that for you. We even built...

Right, withProjectStage should be removed. It's a left-over from DeltaSpike. We could probably introduce a common property `javax.config.projectStage` or so. But in that case you would use `withLookupChain("${javax.config.projectStage}")` to make...

@jmesnil the spec paper should now be in a much better shape. Can you please review if all is resolved? txs!

Hi @rgielen! Thanks for your feedback. Yes, it's not intended to get actively notified asynchronously if anything deep inside the Config changes. It's really just a callback for the case...

Yes, it's fully synchronous on the same thread. That has benefits and of course the downside that you really only get the callback if the getValue() or getOptionalValue() get invoked....

Oh and I got asked for other use cases. The things I've seen is * logging a config value change * creating a new Client after the config changed *...