Metacat

insert OR update system metadata -- no need to do an update right after initial insert...

call the System Metadata generator during upgrade to 2.0.0

In IdentifierManager.updateSystemMetadata(), add a check for invalid system metadata (fields that throw a NullPointerException on access) to ensure that system metadata is populated correctly. Updated calling classes to handle the exception.

Properly initialize the servlet context when starting alternate servlets, which makes sure that the configuration files have been loaded and config properties are available.

Handle SQLExceptions when trying to save system metadata locally.

Convert SQLExceptions to RuntimeExceptions for Hazelcast MapStore operations.

In IdentifierManager, throw SQLExceptions rather than just logging them, and let them be handled higher up in the stack.

use new endpoint/method:
http://mule1.dataone.org/ArchitectureDocs-current/apis/CN_APIs.html#CNReplication.deleteReplicationMetadata

use PUT /obsoletedBy/{pid} for CNCore.setObsoletedBy per our discussion today

Keep the hzIdentifiers set in sync with the Metacat systemmetadata table. If entries are added/updated in the hzSystemMetadata map, make sure the identifier is in the set. If (for some administrative reason) the entry is removed, remove the identifier from the set. This usually doesn't happen.