This is not correlated to the new feature implemented in this branch. It
was needed to compile this version.

Fix changes broken by renaming to ExceptionDummyBackend in DeviceAccess.

They return as soon as the condition is fulfilled, so there is no harm in having long timeouts in case the tests are successful. The only drawback is that it takes longer in case of errors.

		writeAfterOpen writes constants to devices
		remove writeAfterOpen in recovery loop
			that should be in writeRecoveryOpen
		extend testProcessVariableRecovery for constants

  - 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.

forgot to commit latest change: testProcessVariableRecovery now tries to get exception by reading (not writing), currently failing