Hi!

We had great discussions and many valid and important aspects did came up. Too 
bad they were spread all over the place in various threads ;)

So let's again pick up the discussion.

We basically have 2 options. 


1.) a 'contextual' approach like we currently have with our ServiceContext. 
There is exactly 1 Configuration 'per application'. 


2.) a 'builder' approach. The configuration system gets built by the user as 
often as the user likes and in exactly the way the user likes. In that case 
andling the configuration for whole application is _not_ part of this project. 
Means any contextually would need to be provided as @ApplicationScoped producer 
bean or in other ways.

Now it's your turn. Gimme all the pros and cons ;)



LieGrue,
strub

Reply via email to