TeamDev Support : All Content - JxFileWatcher

JxFileWatcher and Network Drives

yuriy.privezentsev@teamdev.com — Tue, 03 Aug 2010 08:50:56 GMT

Hello Steve,

With the JXFileWatcher you can monitor network drives the same as the local drives, keeping in mind limitations that are listed in our release notes: http://support.teamdev.com/community/java_platform_integration_solutions/jxfilewatcher?view=blog

Also, you can quite easily verify yourself whether JxFileWatcher suits your demands by running online its demo: http://www.teamdev.com/jxfilewatcher/onlinedemo/

Regards,

Yuriy.

Client-Server issues, remote filewatcher invocation

roman.kazmin@teamdev.com — Tue, 20 Jul 2010 13:24:52 GMT

Hello Imre,

Could you please confirm that our online demo still able to watch your folder? If it still able to do it, then could you please provide more information about your application ?

Ideally it would be great if you can prepare a small sample application that reproduces this problem at your side and send it to us.

Sincerely,

Roman.

Problem: "ATTENTION: Failed to open file:"

forum-admin@teamdev.com — Thu, 08 Jul 2010 10:23:08 GMT

Hi,

I'm using jxFileWatcher-1.0.2 on Mac OS X Server 10.6.

When I add a lot of file in the directory watched, indications after appear:

8 juil. 2010 12:01:42 com.teamdev.filewatch.mac.KEventWatcher a

ATTENTION: Failed to open file: /xxx/lol.jpg

8 juil. 2010 12:01:42 watch.WatchingAllFileEvents$1 fileAdded

Added[file=/xxx/lol.jpg]

But sometimes, the file isn't added.

So, how I can do to manage this problem.

Thanks.

deleted after renamed

yuriy.privezentsev@teamdev.com — Mon, 21 Jun 2010 15:47:11 GMT

Hi Romain,

This is not expected behavior. FileWatcher should report deleting and then adding the file. We will investigate this issue and provide you with a solution.

Regards,

Yuriy.

Problem while redeploying j2ee web application using jxfile watcher

vaibhav.vyas@thepsi.com — Sat, 01 May 2010 12:11:50 GMT

Thanks, the workaround worked for me.

FileWatcher release file

forum-admin@teamdev.com — Thu, 29 Apr 2010 14:02:52 GMT

Hello (Serge),

Suspicion is that after more than 1 log file is connected to the folder to be watched, I'm not able to release (both) log files properly; Details above

Any ideas, please?

Regards

setFilter & WatchingAttributes

sergei.piletsky@teamdev.com — Wed, 28 Apr 2010 13:29:45 GMT

Hi,

Thanks for the update.

The trouble seems to lies in that folder is deleted before accept() method, as far as i see

No, I do not think so. The problem is that a file system watcher receives all file events post factum. And in case of a file or directory removal it can only receive a FileEvent.Deleted notification plus a file name. At that moment, having only a file name, it is not possible to determine whether it's a file or directory in terms of file system. In fact the File.isDerectory() method returns the 'false' in this case (even if we know for sure that it was a directory before), because that file is already not present in file system.

And your example does not seem to solve this issue as well.

The modified example below demonstrates the issue:

watcher.setFilter(new FileMaskFilter("*.java;*.class") {
    @Override
    public boolean accept(FileEvent e) {
        final File file = e.getFile();
        if (e instanceof FileEvent.Deleted) {
            return super.accept(e);
        } else {
            return file.isDirectory() || super.accept(e);
        }
    }
});

But it does not solve the issue with handling of directory removal events.

After all I think that the solution in this case would be to create two separate instances of file watcher: one should monitor the required files only, and another one - directory names. Of course it's not the best solution, but at least it should meet the requirement.

-Serge

JxFileWatcher Installation Instructions

roman.kazmin@teamdev.com — Fri, 03 Apr 2009 09:23:23 GMT

Installing Library JAR File

JxFileWatcher JAR file should be placed in the application class path.

Note: If your application already uses JNIWrapper library, we recommend using JxFileWatcher without JNIWrapper code inside (jxfilewatcher-<version>.partial.jar).

In this case you will need to have license files for both JNIWrapper and JxFileWatcher libraries.

Installing License File

The JxFileWatcher library requires valid jxfilewatcher.lic license file. Visit TeamDev site (http://www.teamdev.com/jxfilewatcher) to purchase the product or get the distribution package with embedded evaluation license.

The bought License file has to be installed in the META-INF subfolder of any jar library from the application's classpath. Note: you will need to remove the evaluation license from the META-INF folder of the jxfilewatcher-<version>.jar file. To replace the evaluation license with bought license you can use the following Ant script:

        <jar jarfile="jxfilewatcher-1.0.1.jar" update="true">
            <zipfileset file="<path>/jxfilewatcher.lic  prefix=META-INF"/>
        </jar>

Warning: Do NOT rename the license file or it will not be recognized.

Issue with JxFileWatcher and TextEdit on OSX?

sergei.piletsky@teamdev.com — Tue, 03 Nov 2009 13:39:55 GMT

Hi Ian,

Thank you for providing the detailed information about the issue. We will investigate it and let you know the solution.

-Serge

JxFileWatcher 1.0.1 Release Notes

roman.kazmin@teamdev.com — Tue, 04 Aug 2009 14:19:36 GMT

Improvements:

Added JxFileWatcher library jar without JNIWrapper code inside. This version is intended for applications that already use JNIWrapper library.
Added OSGi bundle information.