Project

General

Profile

Bug #4448

KAREntry dependencies should be observed during KAR Cacheing

Added by Aaron Aaron almost 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
core
Target version:
Start date:
10/13/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4448

Description

The lsid dependency mechanism for KAREntries was implemented for opening items from a KAR in the proper order (so a workflow was opened before a Report, which was dependent on the workflow). The cacheing of KAREntries did not have this dependency mechanism and assumed that CacheObjects would be returned properly from the KAREntryHandler regardless of any dependencies. The Reporting module has broken this and we now have a need to insert KAR entries into the cache in the proper order. So a Workflow must go into the cache before a cache object for a report can be returned from the KAREntryHandler. There is a bit of reworking to do on this to get it working properly.

History

#1 Updated by Aaron Aaron almost 10 years ago

Turns out the reporting module did not break this as I had assumed previously. It is a good idea to implement this anyway though. One would assume that the cacheing mechanism would observe the dependencies just as the opening mechanism does now.

#2 Updated by Aaron Aaron almost 10 years ago

KAR lsid dependencies are now observed during cacheing of KAR contents.

#3 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 4448

Also available in: Atom PDF