[
https://issues.apache.org/jira/browse/OWB-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-441.
-------------------------------
Fix Version/s: 1.0.0-alpha-2
(was: 1.0.0-GA)
Resolution: Fixed
> new configuration properties mechanism
> --------------------------------------
>
> Key: OWB-441
> URL: https://issues.apache.org/jira/browse/OWB-441
> Project: OpenWebBeans
> Issue Type: Improvement
> Affects Versions: 1.0.0-alpha-1
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.0.0-alpha-2
>
>
> I like to get rid of our openwebbeans-*.properties and replace them with a
> mechanism where each properties file knows it's 'configuration.ordinal':
> There are still multiple property files for the same configuration (e.g.
> openwebbeans.properties', thus still allowing 'overriding' a configuration.
> But instead of manually looking for defined 'extensions' I just define a
> 'configuration.ordinal' inside the property
> thus I define
> webbeans-impl/ openwebbeans.properties with 'configuration.ordinal=10'
> webbeans-web/ openwebbeans.properties with 'configuration.ordinal=11'
> webbeans-jsf/ openwebbeans.properties with 'configuration.ordinal=12'
> If a properties file doesn't define 'configuration.ordinal' then a value of
> 100
> is assumed.
> The algorithm is easy:
> .) load all properties you can find with the name
> .) sort them via configuration.ordinal in ascending order
> .) overload them as we do already, but instead of some defined names we now
> just
> use the sorted list of properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
