Presented for your approval, the story of a poor little java procedure captured in a twilight zone ...
Before raising my hands and just saying that the NTFS partition is borked, there is some kind of rational explanation for what I see. I have a file with this path
C:\Program Files\Company\product\config\file.xml
I read this file after updating and see something uncomfortable. Eclipse and my Java application still see the old version of this file, and some other programs see the new version. The test that convinced me that it was not my fat finger caused the problem:
In Explorer, I entered the above path, and Explorer displayed the old version . Forcing Explorer to reboot with Ctrl-F5 still gives the old version. This is the behavior that I get in Java. Now in PowerShell type
more "C:\Program Files\Company\product\config\file.xml"
I cut and traveled the path from Explorer to make sure that I am not screwing anything, and shows me the version of the new file.
So, for the programming aspect, there is a cache or some kind of system component that will store this legacy link. Whether I am responsible for checking or reselling for some class of files. I can imagine that someone was “creative” in how the xml files are processed to provide some kind of ringing or whistle. But this may be the case when you are simply ripped off.
Any ideas appreciated ... Thanks!