Bug #3672
closedOpen/Save Workflow as KAR Archive
0%
Description
Workflow fails to be imported from a kar file
I do the following
File->Open File
Choose getting-started/01-SimpleAddition.xml
Then from the File menu of the SimpleAddition workflow
Choose "Export Workflow as Archive (KAR)" and save it somewhere
Close the SimpleAddition workflow
The choose File->Import Archive (KAR)
and navigate to the saved kar file and open it
An error is shown:
"There are no semantic types defined for the actor in this KAR file. Without a semantic type, it cannot be placed in the tree. Please add a semantic type."
Related issues
Updated by Derik Barseghian about 16 years ago
This is very similar to bug #3595, which is the same message but to do with the importing of just an actor kar.
See also discussion in this thread: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/kepler-users/2008-November/000594.html
Updated by ben leinfelder over 15 years ago
we absolutely need to Save and Open KARs that contain:
-1 workflow (MOML)
-1 report layout (ROML)
Updated by ben leinfelder over 15 years ago
related to other bug that is slightly reporting-specific.
same functionality, however
Updated by ben leinfelder over 15 years ago
this is not actually a bug about "Opening" a workflow - it has to do with "Importing"
I'd previously misunderstood. Re-target to 2.0 (unless it's actually fixed?)
Updated by Chad Berkley over 15 years ago
For this bug to be closed, the following functionality should work:
- Save a kar locally and to the local repository
- Upload a kar to a remote repository
- Import an existing kar into the library
- Any LSID conflicts should be handled.
Aaron, are we there yet? It seems like at least most of this was working for the sanparks release.
Updated by Matt Jones over 15 years ago
Import/Export of KARs is now really the Save function, so should be named as such in the menus. Plus complete items from Comment #5.
Updated by ben leinfelder over 15 years ago
I just tried a Save as KAR then Open KAR and got a ClassCastException: looks like we're expecting a KarEntry (a subclass) but getting a JarEntry (the superclass). Workflow doesn't open after this exception is thrown.