[
https://jira.jboss.org/browse/JBTM-787?page=com.atlassian.jira.plugin.sys...
]
Jonathan Halliday commented on JBTM-787:
----------------------------------------
BeanPopulator can now manage multiple instances of the same type. The previous
BeanPopulator.getSingletonInstance(FooEnvironmentBean.class) form is now
BeanPopulator.getDefaultInstance(FooEnvironmentBean.class) and existing properties (file
or system) continue to refer to this instance. For additional instances use
BeanPopulator.getNamedInstance(FooEnvironmentBean.class, "someName") which
corresponds to config properties of the form
"FooEnvironmentBean.someName.propertyName=bar" Note that hardcoded (i.e. in the
java not the embedded properties file) values apply to all instances. Avoid explicitly
using the name 'default' which is used internally for the unnamed bean.
provide bean based configuration, part 4
----------------------------------------
Key: JBTM-787
URL:
https://jira.jboss.org/browse/JBTM-787
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Configuration
Reporter: Jonathan Halliday
Assignee: Jonathan Halliday
Fix For: 4.13.0
The *EnvironmentBean class instances are currently singletons. This causes problems where
we wish to have more than one instance of e.g. an ObjectStore with distinct configuration.
Change the BeanPopulator and associated config file property naming convention such that
we can have multiple instances of a given *Bean type.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira