Metacat

hide the data section unless there is actually data to display

DocumentImpl.delete() now throws finer grained exceptions (not a general exception). Consequently, the classes that call it have been updated to handle the thrown exceptions, including CrudService, ReplicationHandler, and ReplicationService.

refactor the names of these Data Manager implementation classes so that it's easier to use them with the default/local versions of similar. These classes utilize Metacat-specific configuration values rather than relying soley on the bundles that are used in the stand-alone DM lib.

render the <data/> CDATA section in

 - it's a csv string

To support GUIDs in MetacatHandler.handleDeleteAction(), I've added in a new method:
deleteFromMetacat() - deletes a document based on the docid
This factors the deletion code out of handleDeleteAction(). handleDeleteAction() now does a docid lookup based on GUID, and if it is not found, reverts to the deletion based on docid instead.

only include data value/operator when present in the form

refresh search when the data operator changes (changing the value is less clear...keyup event seems too eager)

use correct operators

include data search - new form fields and semQuery schema to allow searching for Characteristics data

turn off the databounds layer by default