MODE-1734 Added unit test to replicate concurrency problem
MODE-1734 Added unit test to replicate concurrency problem
MODE-1734 Corrected 'write-skew' error in Schematic

Added logic to explicitly lock the entry before a copy of the state
is made. Infinispan only allows explicit locks to be used when
PESSIMISTIC locking is enabled, and throws an exception (and rolls
back the transaction) when OPTIMISITIC locking is enabled.
Therefore, the locking is performed conditionally based upon the
cache configuration, though it determined efficiently at startup of
SchematicDb rather than each time a proxy is needed.

See MODE-1734 for much more detail about write-skew and why this
solution works.

With these changes, the concurrent modification tests added in the
previous commit(s) all pass.
MODE-1735 - Updated remove mechanism, so that when deleting federated nodes or above, external nodes aren't deleted; and when deleting projections the segments are cleared on the parent node.
MODE-1735 - Changed the cleanup of federated segments to be done via the parent node.
MODE-1735 - Added a "removeProjection" method on FederationManager, which basically removes a federated segment from a federated node, leaving everything else unchanged.
MODE-1736: Add IronJacamar dependencies into dependency management section
MODE-1736: Remove explicit version reference
MODE-1736: Add jca module assembly descriptor
MODE-1736: Readme, copyright
MODE-1736: Remove already declared dependencies
MODE-1736: Add JCA adaptor directly to binary distribution assembly
MODE-1736: Remove assembly profile
MODE-1736: Move repository to local pom.xml
MODE-1732 - Implemented an mechanism for connectors to provide their own "external binaries" implementation, which aren't stored in the repository's binary store and which the DocumentTranslator "understands"
MODE-1732 - Updated code after rebase on master.
MODE-1732 - Reverted autoboxing for integer values
MODE-1699 Added separate limit for string storage in binary store

Added a separate configuration field to set the minimum size for
string values that should be stored in the binary store. This is
separate from the existing 'minimumBinarySizeInBytes' value,
though it will default to that 'minimumBinarySizeInBytes' value.

All unit and integration tests pass.
MODE-1699 Added AS7 support for minimum string size

Added support to the subsystem for AS7 to separately configure the
minimum size of string values that are to be stored inside the
binary store. Like with the regular JSON configuration, the minimum
string size defaults to whatever the minimum binary size is.
MODE-1699 Refactored common code for AbstractAddBinaryStorage