[BLOSSOM-209] BlossomDispatcherServlet should send BlossomDispatcherInitializedEvent on ApplicationContext refresh Created: 24/May/15 Updated: 03/Jul/15 Resolved: 26/Jun/15 |
|
| Status: | Closed |
| Project: | Blossom |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.7 |
| Type: | Improvement | 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
|
||||||||
| 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 |
|
After a refresh beans have been reinitialized and when running JRebel, Spring Loaded etc, they can have changes in annotations, methods added and so on. Since BlossomDispatcherInitializedEvent is only sent on startup these are not detected. Although, I'm not sure that JRebel does a refresh and Spring Loaded does not. But there are plugins for SL that does. |