If someone includes the Logger into an ApplcationModule and calls writeAll() the Logger variable message will be written. To catch that cases set message empty after calling sendMessage and ignore empty messages in the LoggingModule.

ExceptionHandlingDecorator: With the current (=old) the owner has to be informed about data invalidity as soon as the exception is reported, and then again after recovery.

Fixes #153

improved places where DeviceModule changes testableMode_deviceInitialisationCounter. Now matches with deviceHasError.

Now the writing in the DeviceModule is working.

Fixes #159

Merge iss130 branch into master
Closes #130 

- removed wrong waitForRecovery()
- some code improvements
- fixed wrong logic in doReadTransferAsync

Revert "ExceptionHandlingDecorator: re-introduced while loop. Behaviour is now closer to previous one because it re-tries the read until it succeeds"

Looping the postAction makes no sense. The loop only worked for the transfer itself.

This reverts commit f7f35074.

ExceptionHandlingDecorator: re-introduced while loop. Behaviour is now closer to previous one because it re-tries the read until it succeeds

* doGenericPostAction is void
* removed endless loop in doGenericPostAction
* only wait for recovery if application is running in multi-threaded mode
* fixed return value for doReadTransferXxx in case transfer is not allowed

Fixes #151

	TODO doGenericPostAction
	DONE all the rest

	does not compile, due to missing overrides

This case was missed in #129.

Wip/mhier/129 rearrange device module loop

Initially, devices are closed and hence there is an error message. It goes away shortly when the device got opened. The new behavior is according to specification.

allows to control whether to wait for device recoveries in stepApplication

This prevents stepApplication() to return too early (e.g. right after start) when the device is not yet initialised.

Note: is has been verified that there is no race condition at the beginning despite the counter is only incremented during the test (by introducing an artificial delay at the beginning of handleException()). It works, because testable mode waits until all devices are opened. In testable mode, this check is now equivalent to the devices being also initialised (when the testableModeLock is obtained and the counter is checked).