-import java.io.File;\r
-\r
-import org.simantics.databoard.accessor.Accessor;\r
-import org.simantics.databoard.accessor.CloseableAccessor;\r
-import org.simantics.databoard.accessor.binary.BinaryObject;\r
-import org.simantics.databoard.accessor.error.AccessorException;\r
-import org.simantics.databoard.binding.Binding;\r
-\r
-/**\r
- * File accessor is an interface for data that is located in a file in byte format.\r
- * There are two ways of writing to the files. \r
- * A) Using the writing methods of Accessor+subtypes, eg. setValue, putValue, ...\r
- * They guarantee the value is flushed to the file upon return\r
- * B) Using the write methods of FileAccessor+subtypes, eg. setValueNoflush, putValueNoflush ...\r
- * They do not guarantee flush upon return. Explicit flush() call is required.\r
- * The value resides in memory cache and are available for reading event before flushing.\r
- *\r
- * see FileAccessorExample\r
- * @see BinaryObject File/Memory Byte[] implementation\r
- * @see FileArrayAccessor\r
- * @see FileBooleanAccessor\r
- * @see FileByteAccessor\r
- * @see FileDoubleAccessor\r
- * @see FileFloatAccessor\r
- * @see FileIntegerAccessor\r
- * @see FileLongAccessor\r
- * @see FileMapAccessor\r
- * @see FileOptionalAccessor\r
- * @see FileRecordAccessor\r
- * @see FileStringAccessor\r
- * @see FileUnionAccessor\r
- * @see FileVariantAccessor\r
- * @author Toni Kalajainen <toni.kalajainen@vtt.fi>\r
+import java.io.File;
+
+import org.simantics.databoard.accessor.Accessor;
+import org.simantics.databoard.accessor.CloseableAccessor;
+import org.simantics.databoard.accessor.binary.BinaryObject;
+import org.simantics.databoard.accessor.error.AccessorException;
+import org.simantics.databoard.binding.Binding;
+
+/**
+ * File accessor is an interface for data that is located in a file in byte format.
+ * There are two ways of writing to the files.
+ * A) Using the writing methods of Accessor+subtypes, eg. setValue, putValue, ...
+ * They guarantee the value is flushed to the file upon return
+ * B) Using the write methods of FileAccessor+subtypes, eg. setValueNoflush, putValueNoflush ...
+ * They do not guarantee flush upon return. Explicit flush() call is required.
+ * The value resides in memory cache and are available for reading event before flushing.
+ *
+ * see FileAccessorExample
+ * @see BinaryObject File/Memory Byte[] implementation
+ * @see FileArrayAccessor
+ * @see FileBooleanAccessor
+ * @see FileByteAccessor
+ * @see FileDoubleAccessor
+ * @see FileFloatAccessor
+ * @see FileIntegerAccessor
+ * @see FileLongAccessor
+ * @see FileMapAccessor
+ * @see FileOptionalAccessor
+ * @see FileRecordAccessor
+ * @see FileStringAccessor
+ * @see FileUnionAccessor
+ * @see FileVariantAccessor
+ * @author Toni Kalajainen <toni.kalajainen@vtt.fi>