Bug #2432
closedproblems saving kars from saved actors
0%
Description
When saved RExperession actors or saved Composites are opened, they cannot be saved to the local KAR library. The key point is 'saved' If you build and configure these, they can be immediately saved as KARS. However, if first saved as workflows and then re-opened, you get a 'cannot save as KAR' message!
Related issues
Updated by Dan Higgins over 18 years ago
To reproduce the bug simply open workflows/eco/GARP_SingleSpecies_BestRuleSet.xml. Select the existing saved composite 'Calculate Best Rulesets' actor and try the 'Add to Library' menu command. When you fill in the dialog fields and execute, the "Error building the KAR file: Cannot create trasport KAR: null" appears.
[java] java.lang.NullPointerException
[java] at org.kepler.ksw.KSWBuilder.createKSW(KSWBuilder.java:225)
[java] at org.kepler.ksw.KSWBuilder.createTransportKSW(KSWBuilder.java:
182)
[java] at org.kepler.ksw.KSWBuilder.<init>(KSWBuilder.java:132)
[java] at org.kepler.ksw.KSWBuilder.<init>(KSWBuilder.java:95)
[java] at org.kepler.ksw.gui.CreateKSWDialog$1.actionPerformed(CreateKS
WDialog.java:181)
...
Same thing happens with modified RExpression actors that have been saved to files and then reopened, while composites and modified actors that have never been saved seem to work.
Updated by Chad Berkley over 18 years ago
The reason for this appears to be that the "create composite" menu item was used to create the "Calculate Best Rulesets" composite and thus is does not have an entityId attribute (or any of the other kepler required attributes).
I was not able to reproduce this with an RExpression actor. I created a new workflow, drug an RExpression actor to the canvas, modified the RExpression actor, saved the workflow, closed the workflow, reopened the workflow, then ran "add to library" and it worked fine. The only reason you should get an NPE is if one of the kepler required properties do not exist in the actor. The error handling could probably be a bit better.
I'll leave this bug open for now. If you find another way to reproduce it, add the sequence here and I'll take a look.
Updated by Dan Higgins over 17 years ago
Looks like this bug has been fixed in latest version of Kepler