[MAGNOLIA-2258] Remove dependency on exchange-simple/activation from cache (filter ordering) Created: 14/Jul/08  Updated: 26/Nov/13  Resolved: 15/Nov/13

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: None
Fix Version/s: 4.5.14, 5.1.2, 5.2

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-3178 Several modules have a dependency fro... Closed
relation
is related to MAGNOLIA-2023 filters: cache should be infront of i18n Closed
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:
Sprint: 5.2-rc2

 Description   

This was needed for MAGNOLIA-2023 in order to set the filters order correctly, but isn't the best option since the cache module thus can't order its filters correctly if the exchange-simple module is not present.



 Comments   
Comment by Magnolia International [ 16/Sep/08 ]

Should look into this. the dependency in the module descriptor is now optional but there is still an update and an install task that do
{{FilterOrderingTask("cache", "The cache filter should now be placed before the i18n filter.", new String[]

{"context", "multipartRequest", "activation"}

))}}

  • description seems out of synch with actual code
  • will fail if activation filter isn't there
Comment by Tobias Mattsson [ 15/Nov/13 ]

Thanks to the addition of optionally required filters in MAGNOLIA-3894 this should be easily fix.

Generated at Mon Feb 12 03:34:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.