Bug #4802
closedKARs in KeplerData/workflows are being parsed on startup
0%
Description
When I launch Kepler with a clean cache but with a workflow sitting in my local workflow directory that uses protected KNB data, I am prompted to authenticate.
We should not be prompting people for authentication credentials on startup - only if I try to open the kar file should it be processed.
This used to happen, then it was fixed, now it is back again.
Updated by Aaron Aaron almost 15 years ago
Ben can you email me the workflow that you're having problems with?
Updated by Aaron Aaron over 14 years ago
This only seems to be a problem with KARS that use the ReportLayoutKAREntryHandler.
Updated by ben leinfelder over 14 years ago
I can see the cache() method will eventually call the ObjectManager. is this the culprit that forces parsing of the moml?
ObjectManager om = ObjectManager.getInstance();
NamedObj namedObj = om.getObjectRevision(lsid);
Updated by Aaron Aaron over 14 years ago
ReportLayoutKAREntryHandler.cache
WorkflowManager.getWorkflows
WorkflowManager.initialize
ObjectManager.getObjectRevision
ObjectManager.getObjectFromCache
CacheObjectInterface.getObject
Updated by ben leinfelder over 14 years ago
commented out that bit of code - i believe it is redundant since it is also called in the open() method.
we should keep our eyes out for lost reports and things like that that could crop up as a side effect of not calling this in the cache() method.
I tried this in the gui and on the command line - the reports were still present in both.