Description Daniel U. Thibault 2011-03-30 11:24:46 EDT

Using Eclipse's RSE perspective, I can open a TCF connection to some remote system running the TCF agent, browse the remote file system to a protected file such as /etc/fstab, modify it, and attempt to save the modified version.  I then get a prompt to switch the file to writable from read-only, and acquiesce.  The file property change fails (I get an exception alert [listed below]), but the changes are retained in Eclipse's file editor pane, even if the file is closed and re-opened, and even if the Remote Systems explorer is refreshed and then the file re-opened.  And even if the TCF connection is closed (disconnected) and reopened.  The false changes remain even if I create another (differently-named) connection to the same remote system.  THE (FALSE) CHANGES EVEN SURVIVE AN ECLIPSE RESTART!

At this point I have no clue how to flush this error out.

There is no indication whatsoever that the file contents shown by Eclipse are now completely disconnected from the actual file's contents.  This makes anything the RSE shows through its file service suspect.

The exception alert is:

[TCFC0001E]
TCF command exception:
Command: FileSystem setstat "/etc/fstab",{"Permissions":33206}
Exception: Operation not permitted
Error code: 1
[OK]

Clearly something is badly wrong with Eclipse's caching.  Or RSE's.  Or TCF's.  I just don't know at which level the problem lies.