[BLOSSOM-19] Support for DI and AOP in Content2Bean 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 |
|
By extending Content2BeanTransformer the created bean can use autowiring and be post processed before and after initialization. This enables the created bean to be post processed by all BeanPostProcessors in the root web application context, enabling support for InitializingBean, ServletContextAware, BeanFactoryAware, ApplicationContextAware and so on, including JSR-250 annotations @PostConstruct and @Resource. By modifying Content2BeanProcessor it is also possible to support AOP proxies applied to the created bean. |
| Comments |
| Comment by Jan Haderka [ 06/Dec/14 ] |
|
Bulk close of old resolved issues. |