[ https://issues.jboss.org/browse/JBTM-846?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on JBTM-846: ---------------------------------- A static field can be thought of as a class-scoped variable, and thus a class loader-scoped variable. Given that there is presently a 1:1 mapping between transaction managers and class loaders, all static configuration and state today is by definition applicable per transaction manager. Therefore, if all currently static state is migrated to per-TM state, all present functionality should be preserved. From this perspective, adding new, global-to-all-TM state would be new functionality, and not doing so is preserving the status quo. And thus migrating currently per-TM state to be global state would be a significant behavior change. So I guess what I'm getting at is, I'd recommend that all the currently global state should be associated with the TM state, and not kept global, to preserve current behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira