Discussions
Categories
- 382.6K All Categories
- 2.1K Data
- 212 Big Data Appliance
- 1.9K Data Science
- 448.4K Databases
- 221.1K General Database Discussions
- 3.7K Java and JavaScript in the Database
- 25 Multilingual Engine
- 541 MySQL Community Space
- 469 NoSQL Database
- 7.8K Oracle Database Express Edition (XE)
- 2.9K ORDS, SODA & JSON in the Database
- 499 SQLcl
- 3.9K SQL Developer Data Modeler
- 186.3K SQL & PL/SQL
- 21.1K SQL Developer
- 293.8K Development
- 8 Developer Projects
- 129 Programming Languages
- 290.5K Development Tools
- 96 DevOps
- 3K QA/Testing
- 645.6K Java
- 24 Java Learning Subscription
- 36.9K Database Connectivity
- 151 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.9K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 146 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 200 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 291 LiveLabs
- 36 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.8K Other Languages
- 2.3K Chinese
- 168 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 234 Portuguese
WatchService WatchKey.cancel() is really forever ?
I am using java 8 on linux ubuntu 12.04 following the guidelines Watching a Directory for Changes (The Java™ Tutorials > Essential Classes > Basic I/O)
This works but I notice that once I cancel a watchkey with watchkey.cancel() , I seem to be unable to reenable it again. So I can never watch a directory after I have cancelled the corresponding watchkey (even after reboot ) ?
The API Doc says that " Once cancelled, a watch key remains forever invalid."
What does "forever" mean ? There must be a way to re-watch a dir after the key has been cancelled.
Thanks for your help.
Answers
-
In reply to my request: sorry , I had a logical error in my test case that did not clean up the to-be-watched directory structure correctly.
Remains the question: what is "forever" ? Until a new watchservice is created ?
Sorry for the noise.
-
Registering recursively will work as Sotirios has indicated. This effectively registers each directory/sub-directory that currently exists.
You can alternatively import and use *com.sun.nio.file.ExtendedWatchEventModifier.FILE_TREE* as in:
<span class="pln" style="background: transparent;">dir</span><span class="pun" style="background: transparent;">.</span><span class="kwd" style="color: #00008b; background: transparent;">register</span><span class="pun" style="background: transparent;">(</span><span class="pln" style="background: transparent;">watcher</span><span class="pun" style="background: transparent;">,</span><span class="pln" style="background: transparent;"> standardEventsArray</span><span class="pun" style="background: transparent;">,</span><span class="pln" style="background: transparent;"> </span><span class="typ" style="color: #2b91af; background: transparent;">ExtendedWatchEventModifier</span><span class="pun" style="background: transparent;">.</span><span class="pln" style="background: transparent;">FILE_TREE</span><span class="pun" style="background: transparent;">);</span>
This will watch the entire sub-tree for change AND account for added directories and sub-directories.
Otherwise you will have to monitor for any new directories/sub-directories and register them also. There can also be an issue with deleting parts of the directory hierarchy since each registered directory has a handle watching it so the (lowest) sub-directories need to be removed first when deleting parts of the structure.