local repositories not showing up in components tree
Summary says it all. I'm at r21772, and the default workflows repository isn't in the components tree. Adding repositories doesn't do anything. I'm not even getting prompts to sign into KNB or DEV to cache data.
#1 Updated by Aaron Aaron over 12 years ago
Yeah this is an interesting artifact of the new way the Component Library is built. I'm not sure if this is a bug or not yet. Thought I'd leave it that way for a little bit to see how people felt about it.
The way it works now is only paths to components in the library exist. So if you save a KAR file into the workflows folder then it will appear in the library. Otherwise the Workflows folder does not show up there. You will also notice the same behavior in the Ontologies. An ontology and ontology classes will only show there if there is a component in the local repositories that has been tagged with that SemanticType.
Anyway, use it this way for a little while and tell me what you think.
All the ontologies are now showing in teh Drop down box just above the component tree, so you can still see all of them there. And that list should now be getting updated when you add/remove a local repository.
#2 Updated by Oliver Soong over 12 years ago
Well, I'm now seeing the described behavior at r21780, but I'm missing a KAR. I've got one that's just the MOML and ROML, and another that's a run archive (MOML, ROML, run, pdf). I'm only seeing the run archive. This may be because the two KAR files share the same MOML and ROML (identical LSIDs), so this may be related to bug 4512.
#4 Updated by Oliver Soong over 12 years ago
I deleted the run archive from the repository and restarted Kepler, but the report archive (MOML and ROML only) still doesn't show. I was under the impression that Kepler would re-sync the repositories on startup, but just in case I did a clean-cache and it still says no components found.
#5 Updated by Oliver Soong over 12 years ago
This is slightly more complicated. I restarted Kepler again, and now both KARs show up in the components tree.
So starting from a clean-cache:
1. Only report archive (MOML & ROML) in the folder.
2. Added local repository. No components found.
3. Restarted Kepler. Component found.
4. Put run archive back in folder (MOML, ROML, run, & pdf).
5. Sources->Build. Only the 1 component found.
6. Restarted Kepler. Both components found.
#10 Updated by Oliver Soong over 12 years ago
I think this bug is partly due to bug 4512, partly due to the new hiding empty repositories "feature", partly due to changes in the KAR structure, and partly due to an ordering problem. There's also another slightly separate problem with local repository content not being added properly (differences between adding repositories from within Kepler and rebuilding the cache on Kepler startup), so that I have to close and restart Kepler before it finds any components.
So to explain. The tpc01 report archive contains an entity "ROML" and "tpc01-buffalo-tb" (the MOML). The tpc01 run archive contains those two entities as well as "RIO" and "WorkflowRun". Because of bug 4512, if the run archive is added to the cache first, then there is no new content in the report archive, and so the new functionality hides it.
If the report archive is added first, then the run archive adds some new content (but no new MOML or ROML) and is shown. I'm not sure why that triggers bug 4563.
There seems to have been a change in the way ROML is stored. If I generate a new pair of report and run archives, the report archive contains "test" (the MOML) and "test_ROML". On the other hand, the run archive contains "RIO", "WorkflowRun", and "ROML" in addition to "test" but no "test_ROML". The LSIDs for test_ROML and ROML also differ, even though the reports themselves never changed.
I think this is all due to the contents of MANIFEST.MF in the KARs and the names coming out of it. As far as I can tell, the names that show up in the components tree are the names in MANIFEST.MF truncated to the first dot (.). The name for the ROML used to be identical between the run and report archives, but now it differs. Also, the tpc01 run archive seems to contain 2 entries for the ROML with different names but the same LSID. The test run archive seems not to have that problem.
#11 Updated by Oliver Soong over 12 years ago
Fixing bug 4512 solves part of the problem, but some others remain and there are some new ones. I'm still following the instructions from Comment 5.
The problem shown in step 2 (no components after adding local repository) still exists.
In step 3, the component is found as before, but now it only contains the MOML, even though the KAR file itself has both MOML and ROML.
In step 6, both components are found and both contain MOML, but neither show the ROML, even though it is definitely in the KAR.