-waitting for recovery is now outsourced in function
	DeviceModule::waitForRecovery()

	-everywhere where the function is called, the new function is now called.

- The direction cannot be determined from the accessor which is being decorated
- Fixed wrong usage of feeding/consuming in Applicaton::createDeviceVariable. Was used consistently wrong, so there was no behaviour bug. But the code was confusing because the direction was wrong.

Tests still failing.

- All accessors come up in exception state.
- Read-accessors increase counter in init phase

Assertion is gone, but tests still failing

  - EntityOwner has individual counters for both events
  - Adapted all instances of increment/decrementDataFaultCounter
  - Not changed getDataValidity() implementation yet
  - Tests failing

- Exception handling decorator does not allow to leave testable mode before
  devices are up
- Test facility makes sure that testable mode counter is zero at the end of startApplication()

wip #47: register accessor for write after open in DeviceModule if write cannot be performed in initialisation phase

change declaration of 'decrementDataFaultCounter' in 'EntityOwner' to take a bool parameter and adjust rest of the code to it
implement 'decrementDataFaultCounter' in 'ApplicationModule' according to ticket #95 -> rewrite all outputs when 'faultCounter' goes from 1 to 0

remove commented part of ExceptionHandlingDecorator - 'void doPreRead() override' and its implementation

removed doPreRead() / doPreWrite() , doPostRead() / doPostWrite() from ExceptionHandlingDecorator - tests are now failing

  - Handle illegal writes to read-only accessors in doPreWrite().
    Otherwise, attempting to write to the recovery accessor would result
    in a nullpointer access.
  - Related test case.

  - Cleaned up comments
  - Place using-declaration of buffer_2D to class definition so the base
    class name can be omitted in the implementation

- remove "void ExceptionHandlingDecorator::setDataValidity(DataValidity newValidity)"
- add "void ExceptionHandlingDecorator::setOwner(EntityOwner* owner)" and remove owner setting in constructor

  - Cleanup:

    - Reorder code in Application::createDeviceVariable
    - Separated ExceptionHandlingDecorator constructors for writable and
      non-writable registers
    - cleaned up doPreWrite

- New flag parameter for ExceptionHandlingDecorator::genericTransfer.
  Method does not invalidate data if flag invalidateOnFailure is set to
  false.
- Write related methods in ExceptionHandlingDecorator set
  invalidateOnFailure flag to false

Changes resolve ticket #57.

  - First compiling version, tests pass, hope it works...
  - Needs some tweaking

- Exception handling decorator and ThreadedFanOut send condition variable notificatios via the DeviceModule
- FanOut sends terminate to impl and all slaves.
Solves (some?) shutdown issues, but breaks bi-directional array test.

Otherwise it is impossible to shut-down the server if the device could
not be opened at all or is in constant error state

Fixes #39

Test still does not work.
-Unable to get the exception status for the device throwing exception.
-Second device only works it has it's own trigger.

 - Have a ZMQ push-type variable from a DOOCS-backed device that is NOT
   used as a trigger (otherwise the bug does not happen)
 - Connect that to an ScalarPushInput in an ApplicationModule
 - call readAnyGroup() from the ApplicationModule's main method

=> ReadAnyGroup.finalise() will cause an infinite recursion between
ExceptionHandlingDecorator::doReadTransferAsync and
TransferElement::readAsync because of wrong dispatching to the decorated
type

  DeviceModule and ControlSystemModule now do not take the optional prefix argument in their constructors any more. Use the [] operator instead to get the submodule.

- Add ExceptionHandlingDecorator and decorate all device variables with it.