Added a user persistence provider handling database requests from user

The new UserPersistenceProvider is used to create a persistence provider
for a database access for a given user. The problem is splitted database
for each user. As the sopeco-service must be REST, the database
connection has to established and closed every time a request is made to
the service.
The UserPersistenceProvider gives database access directly via a token,
which each user gets after login.

The account connection for mapping is done after login. This is required
to get the account connected to a user afterwards to change the account
database.



TODO: The token has to removed after a finite time slice.
TODO: Database password for each user is now stored plain text in the
spcsvc database




Change-Id: Ife4f71ec085a615487c8653a078bd7dd142be143
Signed-off-by: Peter Merkert <p.merkert@sap.com>
Cleaned the database and removed unused debug stuff.

Remove the unused FleixblePersistenceProvider, whose function is now in
the UserPersistenceProvider.
Remove some debug lines in the UserPersistenceProvider.

Deleted the database once, because the schema was changed: Now the
database password for the account database is stored as plain text in
the spcspv database.

Change-Id: I1138d541a4390f94bd2311dc55df5a1fd6a0baa4
Signed-off-by: Peter Merkert <p.merkert@sap.com>
Fixed a scneario add REST service to have more possiblities to add a new
scenario.

Before a scneario could be added only with name, specname, token and an
ExperimentSeriesDefinition. The other method, to create a scenario with
token and ScnearioDefinition did not work as it had the exact same
Jersey signature.
Now the first method is transformed with a pathparam for the name. This
is not a beautiful fix, but it's the only possiblity as Jersey does not
support method overloading!
(https://java.net/jira/browse/JERSEY-645)
(http://stackoverflow.com/questions/10030045/how-can-i-overload-a-method-with-queryparam-in-jersey-spring)

Change-Id: If49f31cc49a136990973a67e8c9a5ebf4b61ed0b
Signed-off-by: Peter Merkert <p.merkert@sap.com>
Tried to add a test to pass a SCenarioDefinition to create a new
scenario - but failed.

I have no clue, why the commented out test case to test the REST service
for creating a scenario based on a ScenarioDefinition fails. The test
fails calling the REST service. So there is anything wrong with the
parameter at the moment.

Change-Id: I4204845c9a4c681ec9f7382ac1378b6810ebb69c
Signed-off-by: Peter Merkert <p.merkert@sap.com>
Added an Unittest for the UserPersistenceTest.


Change-Id: I01d55ade8a9c9b2360a911526ab590fb0e9966bc
Signed-off-by: Peter Merkert <p.merkert@sap.com>
Added test for scenario addition and blocks addition of scenarios with
same name now. Added a listing for all the scenarios (names) avaiable.

The name check is added to the REST services (see Scenario.java).

The scenario lists can be requested with a new REST service. The service
has been added to the ServiceConfiguration.

Added a test for the scenariolisting.

Change-Id: I97afadb8056b91ba2a679061f338452527b030e0
Signed-off-by: Peter Merkert <p.merkert@sap.com>
Scenario deletion added to the project.

Added a scenario deletion REST service.

TODO: Cannot connect to user database any more. This is quite a heavy
issue and need to be investigated.

Change-Id: If9366003131e1775f5d7c0e1b23ec76c32a7af50
Signed-off-by: Peter Merkert <p.merkert@sap.com>
Added a scenario switch REST service.

Added the scenario switch method with a test to the project.

Change-Id: Ie8430a34f3a9c196c5fd0a0d59e7eaaff7361d34
Signed-off-by: Peter Merkert <p.merkert@sap.com>