[BLOSSOM-17] Apply preexecution proxies using a BeanPostProcessor instead of manual configuration Created: 25/Sep/10 Updated: 19/Dec/14 Resolved: 19/Dec/14 |
|
| Status: | Closed |
| Project: | Blossom |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Tobias Mattsson | Assignee: | Tobias Mattsson |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Patch included: |
Yes
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Description |
|
Instead of requiring users to manually configure the BlossomHandlerMapping in their beans xml Blossom should detect them automatically with a BeanPostProcessor. This also allows Blossom to detect the default HandlerMapping that is now missed. |
| Comments |
| Comment by Tobias Mattsson [ 19/Dec/14 ] |
|
The only real benefit of adopting this would be reducing the configuration in necessary minimally. To support existing configurations Blossom would need to be backwards compatible, identifying and ignoring such configurations. Otherwise users would have to update their xml when upgrading. Closing as Won't fix because of the limited benefit. |