"jhalliday" wrote : In an effort to better accommodate the assorted bean-centric configuration and dependency wiring frameworks (e.g. Spring, MC) I'm considering further changes to the way TS internals are configured. | | [... snip ...] | | What I'd like to do is introduce a per-module EnvironmentBean, | | [... snip ...] | | Interesting re: the consideration to "accommodate ... assorted ... dependency wiring frameworks". 1. Do any current (or past considered) parts of the TS internals' code make use of DI Singleton Beans? 2. If answer to #1 is "Yes", is it true that those TS Singleton Beans are bound exclusively to the Spring framework API (as its lone DI provider)? 3. Would the implementation of the new per-module EnvironmentBeans give any priority to considering non-Spring DI APIs (especially e.g. Guice)? 4. Is there any value (beyond academic) to considering a "DI-provider independent" approach to building these (and potentially future) TS Singleton Beans? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246049#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...