Metacat

generateMissingSystemMetadata was swallowing Exceptions instead of throwing. Refactored so that specific exceptions are thrown, affecting [create/update]SystemMetadata methods, too.

committing changes related to the new restservice update specification (newPid vs. obsoletedGuid)

replace whitespace in generated docid scope (sanparks patch from 1.9.4 branch)

use outputstream as an object, not a string. relax the Map typing to allow for mixed values. (sanparks patch)

use "object_format" element consistently so that it is replicated across instances
https://redmine.dataone.org/issues/1514

remove very old "metacat webservice" code - as far as i can tell it is never referenced or used. plus we have eocgrid and the new D1 rest services covering this territory now

zero padded date string in DocumentUtil.generateDocumentId() for readability

Use SystemUtil.getContextURL() in ResourceHandler to construct the DataONE service URL (rather than direct calls to PropertyService). This handles http and https URLs, and strips the :80 or :443 for the well known ports.

Minor changes to MetacatHandler:
- Improved logging where MetaCatServlet.class was used in getLogger() rather than MetacatHandler.class (holdover from the refactor)
- Minor formatting changes, and replacement of 'MetaCatServlet' with 'MetacatHandler' in the logging output as needed.

improved multipart handling (improved logging messages, code, and error checking). Added exception classname to error output when the generic Exception is thrown. Added error check for cases of null value for file parts 'sysmeta' and 'object.'