fixed test, re-enabled.
Updating the test to use the returned localname, instead of hard-coded.
Notes on bugs I found in existdb
rewrite incrementer to be thread safe, and make it not block the main
processing thread while it stores the new value back to the DB.
Update these tests to use the returned Local ID, rather than hardcoding
what the id is expected to be.  Also fixed a bug in two tests where they
were doing a lookup by URI when the test was supposed to be doing a
lookup by  name - wasn't caught because the name and URI were identical.
update the test cleanup code so it doesn't try to do a removeCollection
that causes issues for existDB, also, ensure we don't deadlock the DB by
doing a write while remove request is sent.
update the test cleanup code so it doesn't try to do a removeCollection
that causes issues for existDB, also, ensure we don't deadlock the DB by
doing a write while remove request is sent.
remove some unused code
Rework the change set processing.  These changes:

1) Enable multi-threaded processing of the changes for certain types of
change sets.

2) Enable updating the the change set xml document in-place - rather
than getting the xml, deserializing, updating, serializing, and storing
the document for each change in the change set.  This helps performance
a little bit there still is room for improvement here based on
conversations on the existdb mailing list.

3) Enable a 'bulk load mode' for processing a complete changeset xml
document.  During bulk load mode, all updates to the change set document
that will be stored in the DB are held in memory until the entire change
set is processed - and then written once at the end.  This (combined
with 1) give a massive improvement in performance compared to 2).  This
prevents existDB from thrashing about while indexing and deleting the
same content over and over again.
formatting
clean up the test code that was cleaning the existDB between tests.
This commit does the upgrade to existDB 2.1.  

There are still some library issues to work out - currently, this only
runs within OSGI if the XML libraries are updated in the
jre/lib/extensions folder.

The necessary libraries are included in the zip file
'endorsed-for-jre-lib-folders.zip'

There are a few TODOs in this code that I still need to discuss with
Kevin.

The required configuration for existDB has changed - see the included
suggested-conf.xml for the current suggested configuration.