When using Java's FileLock, is it ok to let close() to automatically do a lock.release()?

As most should know `close()` also closes any streams uses. This allows the follow code: BufferedReader br = new BufferedReader(new InputStreamReader(new FileInputStream(...))); ... br.close(); This is nice, since we don't need a reference to `FileInputStream` and remember to close it. But does it also work for `FileLock`s? final FileInputStream fis = new FileInputStream(new File("buffer.txt")); final FileChannel c = fis.getChannel(); final FileLock lock = c.lock(0L, Long.MAX_VALUE, true); final BufferedReader br = new BufferedReader(new InputStreamReader(fis)); try { while(br.ready()) { System.out.println(br.readLine()); } } finally { br.close(); } I've tried this code and the lock is correctly released when `br.close()` is called, but is is safe to do so? The [Closeable JavaDoc][1] says, *"Closes this stream and releases any system resources associated with it."* Am I safe to assume that I am using `close()` as specified to `release()` the lock? [1]: http://java.sun.com/javase/6/docs/api/java/io/Closeable.html#close()

以上就是When using Java's FileLock, is it ok to let close() to automatically do a lock.release()?的详细内容,更多请关注web前端其它相关文章!

赞(0) 打赏
未经允许不得转载:web前端首页 » JavaScript 答疑

评论 抢沙发

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址

前端开发相关广告投放 更专业 更精准

联系我们

觉得文章有用就打赏一下文章作者

支付宝扫一扫打赏

微信扫一扫打赏