commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Brook (JIRA)" <j...@apache.org>
Subject [jira] Updated: (VFS-238) DefaultFileMonitor fails to notice file creations, or re-creations
Date Wed, 11 Feb 2009 20:53:02 GMT

     [ https://issues.apache.org/jira/browse/VFS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andy Brook updated VFS-238:
---------------------------

    Description: 
As title, 
{code}
		FileSystemManager fsManager = VFS.getManager();
		FileObject listendir = fsManager.resolveFile("/tmp/test.txt");
		
		fFileMonitor = new DefaultFileMonitor(new MailboxFileListener(this)); 
		fFileMonitor.setRecursive(true); 
		fFileMonitor.addFile(listendir);
		fFileMonitor.start(); 
{code}
h3. Uncreated initial state
# If the file does not exist before the above is run, no 'create' even is fired when it is
subsequently created.

h3. Recreation use-case
# If 'test.txt' exists, notifications of updates are generated as expected.  
# If I now remove the file, I get a delete notification - as expected
# If I now re-create the file, I get no notifications, even if updating.

So this kind of breaks for me, the same behaviour was in the maven 2005.. jars.

Am I misunderstanding what the DefaultFileMonitor is supposed to do?


  was:
As title, 
{code}
		FileSystemManager fsManager = VFS.getManager();
		FileObject listendir = fsManager.resolveFile("/tmp/test.txt");
		
		fFileMonitor = new DefaultFileMonitor(new MailboxFileListener(this)); 
		fFileMonitor.setRecursive(true); 
		fFileMonitor.addFile(listendir);
		fFileMonitor.start(); 
{code}
h3. Uncreated initial state
# If the file does not exist before the above is run, no 'create' even is fired when it does.

h3. Recreation use-case
# If 'test.txt' exists, notifications of updates are generated as expected.  
# If I now remove the file, I get a delete notification - as expected
# If I now re-create the file, I get no notifications, even if updating.

So this kind of breaks for me, the same behaviour was in the maven 2005.. jars.

Am I misunderstanding what the DefaultFileMonitor is supposed to do?



> DefaultFileMonitor fails to notice file creations, or re-creations
> ------------------------------------------------------------------
>
>                 Key: VFS-238
>                 URL: https://issues.apache.org/jira/browse/VFS-238
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: linux, amd64 (ubuntu 8.10)
>            Reporter: Andy Brook
>
> As title, 
> {code}
> 		FileSystemManager fsManager = VFS.getManager();
> 		FileObject listendir = fsManager.resolveFile("/tmp/test.txt");
> 		
> 		fFileMonitor = new DefaultFileMonitor(new MailboxFileListener(this)); 
> 		fFileMonitor.setRecursive(true); 
> 		fFileMonitor.addFile(listendir);
> 		fFileMonitor.start(); 
> {code}
> h3. Uncreated initial state
> # If the file does not exist before the above is run, no 'create' even is fired when
it is subsequently created.
> h3. Recreation use-case
> # If 'test.txt' exists, notifications of updates are generated as expected.  
> # If I now remove the file, I get a delete notification - as expected
> # If I now re-create the file, I get no notifications, even if updating.
> So this kind of breaks for me, the same behaviour was in the maven 2005.. jars.
> Am I misunderstanding what the DefaultFileMonitor is supposed to do?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message