The executionwas not working right: A scheduledexperiment was deleted
out of the database and it was not implemented to find the execution
details for a scenario just with the experiment key. The experiment
query has been added to the ExecutedExperimentDetails. The
ExecutionScheduler now also checks the database
ExecutedExperimentDetails for the searched scheduled experiment.

Change-Id: Ib6c22f25d9066b0a1cdf933c05300546e0239df0
Signed-off-by: d061465 <p.merkert@sap.com>
When scheduling an active experiment, still the ID of the
ScheduledExperiment was retunred. This is now fixed to return the
experiment key.

Change-Id: I2368fac722f76bd4f35330e92ce0644095b123c4
Signed-off-by: d061465 <p.merkert@sap.com>
Fixed bug, that JPA NamedQuery expected experimnetKey as String, but was
passed as a Long.

The ScheduledExperiment now return a long for the experiment key. At the
moment it still only refers to the hashCode() method, which returns an
Integer, but this might change later.

Change-Id: I79cf0c70bf290ecdd5a3cd85b7504e3303d17ffb
Signed-off-by: d061465 <p.merkert@sap.com>
Fixed a fetch for ExecutedExperimentDetails.

Change-Id: Ib0b4fae64d93b011894d800e2f5557934dbc8106
Signed-off-by: d061465 <p.merkert@sap.com>
Fixed a bug when collection information about the current experiment
status. Now the status is filled with correct data.

Change-Id: Ib34a560518d768e63f36e90b5294f01d53735a09
Signed-off-by: d061465 <p.merkert@sap.com>
Fixed the ExperimentStatus package building process, when the experiment
is still a ScheduledExperiment. Now the label is set correctly and the
starttime is set accordingly.

Change-Id: I6466ac6df24bcfdda8b4804a93fd8bbed8d5bd89
Signed-off-by: d061465 <p.merkert@sap.com>