This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 23079 - There is no way how to find out, that FileSystem is invalid
Summary: There is no way how to find out, that FileSystem is invalid
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks: 18988
  Show dependency tree
 
Reported: 2002-05-03 08:28 UTC by rmatous
Modified: 2010-04-02 16:11 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description rmatous 2002-05-03 08:28:47 UTC 
There is no way how to find out, that  FileSystem
is invalid. Semantic of existing final method
FileSystem.isValid has a little different
meaning(snip from javadoc: "Generally invalidity
would be caused by a name conflict in the
filesystem pool."). This method can`t be final.

snip from jglick contribution to openide-dev:
Suggestion:
 
 1. Make isValid non-final.
 
 2. Make the default impl always return true.
 
 3. Override sensible in LocalFileSystem,
JarFileSystem, etc.
Comment 1 Marek Grummich 2002-07-22 11:15:38 UTC 
Set target milestone to TBD
Comment 2 Marek Grummich 2002-07-22 11:18:44 UTC 
Set target milestone to TBD
Comment 3 Antonin Nebuzelsky 2008-04-15 17:02:08 UTC 
Reassigning to new module owner jskrivanek.
Comment 4 Jaroslav Tulach 2010-04-02 16:11:20 UTC 
In the new era of masterfs (which is always valid), I see no need for this enhancement.