[MAGNOLIA-5634] SecuritySupport will always be null when accessed prior to being initialized Created: 23/Jan/14 Updated: 11/Mar/16 Resolved: 23/Jan/14 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.2 |
| Type: | Improvement | Priority: | Critical |
| Reporter: | Daniel Lipp | Assignee: | Daniel Lipp |
| 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)
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
With Best would be to define a default implementation for SecuritySupport that's just to be used in the initialization phase and will then be replaced by the configured one, once the later is available. We anyway know that for the initialization phase there's only one super -> the superuser. |
| Comments |
| Comment by Magnolia International [ 24/Jan/14 ] |
|
Fixed by implementing a custom ObservedComponentFactory for SecuritySupport which returns a temporary instance until the configured one is available. |