Hi, Yep, this was an issue for me too :-)
Mario, I know that the caching mechanism has high priority for VFS 1.1, but what if until than we would have a utility class (say NonCachedFileOperations) for file operations that require non-cached file information? For instance in JCommander we resorted to writing wrappers for methods like getChildren(), delete() and mkdir() in which we call the close() method for the involved files or the parents of the involved files. Later on, in order not to break backward compatibility, as the caching issue is architecturally fixed, these wrapper methods would have the close() calls removed. The utility class might be a better solution than to inline the close() calls to the client code. Regards, Robert On 3/30/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote: > > Hi! > > I have an empty directory : AbstractFileObject#children = [] > > Then, some files are written inside, but children is still set to [] > > Thus, AbstractFileObject#getChildren() still gives [] > > > > I'd like to flush this damned cache, but everything is private :( > :-) Its by far the most asked question. > > call directory.close() - this will refresh the cache too. > > Ciao, > Mario > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
