Morpho

This happened to me for three additional dps: connolly.287.1, connolly.281.1,
connolly.274.1.

I experienced the same thing that Veronique reported using Morpho. This appears to only happen with data packages that have imported data tables. Save these data packages locally then make a change to them. Next time they are saved locally and to the network this error comes up in the Morpho stderr.log.

Name: action => update
Name: public => no
message from server:
<error>
Error in EMLSaxHandler.startElement UPDATE
</error>

MetacatUpload Exception in EML200DataPackage!

<error>
Error in EMLSaxHandler.startElement UPDATE
</error>

Problem Saving

<error>
Error in EMLSaxHandler.startElement UPDATE
</error>

This error does not occur with data packages that do not include an imported data table. I saved a few data packages locally, then made changes. Afterwards I saved again locally and to the network. ltderr.log reports that they update sucessfully. Morpho responds and updates correctly.
...
Name: action => update
Name: public => no
message from server:
<success>
<docid>bowdish.790.2</docid>
</success>

It takes two trys to update a data package with a table, when it has been saved locally first. The first time Morpho gets stuck and the error appears in the stderr.log.

Cannot reproduce with v1.8.0. Steps:
-Duplicate jscientist package
-Remove data table
-Import new sample data table
-save locally
-change title
-save locally (rev now 2)
-save to dev metacat
-local and remote have same docid/rev.

Original Bugzilla ID was 2287