[MGNLDMS-146] Repository name for cache flushing is registered at wrong path Created: 26/Nov/08  Updated: 03/Jul/14  Resolved: 23/Jan/09

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: 1.2.6
Fix Version/s: 1.2.7, 1.3

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLDMS-141 Cache doesn't getting flushed by defa... Closed
dependency
depends upon MAGNOLIA-2515 Update task for removing modules/cach... Closed
duplicate
is duplicated by MGNLRES-1 Layout workspace name for cache flush... Closed
relation
is related to MAGNOLIA-2490 Provide common task for modules to re... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Currently DMS registers its name for cache flushing upon activation at /modules/cache/config/repositories instead of /modules/cache/config/configurations/default/flushPolicy/repositories



 Comments   
Comment by Jan Haderka [ 26/Nov/08 ]

r20167

Comment by Magnolia International [ 22/Jan/09 ]

Several issues:

  • /modules/cache/config/repositories is still there on a clean 3.6.3 (dms 1.2.6) instance, see MAGNOLIA-2515. Fresh install of dms 1.2.7 does not create this anymore, but an update should remove it. Additionally cache 3.6.4 should remove it (and/or checks that no other repos are in there)
  • The dms has an optional dependency on the cache module, but the version handler class will not be useable if the cache binaries are not on the classpath (usage of RegisterWorkspaceForCacheFlushingTask)
Comment by Jan Haderka [ 23/Jan/09 ]

Added install task to remove old configuration and made dependency non optional.

Generated at Mon Feb 12 00:48:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.