[BLOSSOM-20] FactoryBeans for creating beans configured in repository with support for observed reloading Created: 25/Oct/10 Updated: 06/Dec/14 Resolved: 14/Dec/10 |
|
| Status: | Closed |
| Project: | Blossom |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.2 |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Tobias Mattsson | Assignee: | Tobias Mattsson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Two FactoryBeans, one for simply creating the bean from configuration, the other with additional support for reloading transparently when the content changes. The bean is disposed using the callbacks supported by the ApplicationContext in which the bean has been loaded. This means both DisposableBean and @PreDestroy is supported. These however is only supported on the top level bean not on inner beans. |
| Comments |
| Comment by Tobias Mattsson [ 28/Oct/10 ] |
|
It could be a good idea to provide a special tag in the blossom namespace, something like this: <blossom:configured-bean id="discountService" repository="config" path="/modules/mymodule/beans/discountService"/>
|
| Comment by Jan Haderka [ 06/Dec/14 ] |
|
Bulk close of old resolved issues. |