Great everything works fine now!
Thanks for your help and patience, commons-VFS is really usefull.
Bye,
-eric
Mario Ivankovits wrote:
Hi Eric!
FileSystemManager fsManager= VFS.getManager();
This code works the first time but not the second times after I have
deleted the di
Hi Eric!
FileSystemManager fsManager= VFS.getManager();
This code works the first time but not the second times after I have
deleted the directory dest.
Ok, yes I see, it IS on my list for the next VFS version.
A better workaround (if you do not need VFS as singleton) is to c
Hi,
I'm sorry Mario I did not receive "my" post neither your answer (and I
needed to switch to another mail accounts).
Big thanks for your help, I did not see the close() function.
Your suggestion works in the testcase, unfortunattely this does not work
for me as I copy from one fileobbject t
Hi!
With commons-vfs RC6, I experience sometimes the following exception :
Could not write to "file:///tmp/test/file3.txt" because it is read-only.
I've already answered it.
The current solution is to call file3.close() after the second resolveFile.
---
Mario
-
Hi,
With commons-vfs RC6, I experience sometimes the following exception :
Could not write to "file:///tmp/test/file3.txt" because it is read-only.
I found the cause of this exception, this happens when :
1. a file (file1.txt) is copied to a directory (/tmp/test/) containing
the destination fil
Hi Eric!
With commons-vfs RC6, I experience sometimes the following exception :
Could not write to "file:///tmp/test/file3.txt" because it is read-only.
This again has something to do with the internal vfs cache.
throws Exception {
FileSystemManager fsManager = VFS.getManager()
Hi,
With commons-vfs RC6, I experience sometimes the following exception :
Could not write to "file:///tmp/test/file3.txt" because it is read-only.
I found the cause of this exception, this happens when :
1. a file (file1.txt) is copied to a directory (/tmp/test/) containing
the destination fil
