[ADCOM-2] Implement a mechanism to handle direct calls to cache Created: 26/Feb/20 Updated: 04/Mar/20 Resolved: 04/Mar/20 |
|
| Status: | Closed |
| Project: | Addon Commons (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Ilgun Ilgun | Assignee: | Ilgun Ilgun |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.25h | ||
| 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)
|
||||||||
| Documentation update required: |
Yes
|
||||||||
| Epic Link: | DAMs backend | ||||||||
| Sprint: | Add-Ons 32 | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
Currently, annotations such as CacheEvict looks to be working only in some cases where we have Guice constructing the object. For instance, in module classes, it doesn't intercept the call for some reason that we don't know yet. Either we have to fix that annotation to work everywhere across the codebase or we need an injectable mechanism which provides API to let us invalidate the cache in the downstream.
AC
|