[jboss-dev-forums] [Design of JBoss Transaction Services] - Re: beanifying the config

[jhalliday]

So next time I casually mention I'm thinking of changing the configuration system, please stop me.  Turns out there are (drum roll please...) not less than 120 configuration properties in the codebase. Not counting XTS. Got to love IDEs with refactoring support.

In place of the old config properties (and yes Mark, they are still there for backward compatibility) we now have a set of configuration beans as described previously. In general it's one per module, which the exception of ArjunaCore/arjuna which has four.

Almost all the code now uses the beans rather than accessing the property manager directly. Indeed I'm tempted to ditch the property manager entirely, but first we need to figure out if/how we want to handle persistent configuration changes.

Meanwhile there is just the marathon task of documenting each and every property. Any volunteers? :-)

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249662#4249662

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249662