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 19260 - better Data Systems reactions on File Systems changes
Summary: better Data Systems reactions on File Systems changes
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker (vote)
Assignee: Jiri Skrivanek
URL:
Keywords: API, ARCH
Depends on:
Blocks:
 
Reported: 2002-01-10 10:36 UTC by David Simonek
Modified: 2008-12-22 09:50 UTC (History)
5 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Simonek 2002-01-10 10:36:56 UTC
Situation: Module code listens to filesystem's events and wants to do something
with data systems in reaction on these events -> causes bug troubles now,
because data systems are notified in the same way as client code in module is.
That means that data systems can be notified and updated *after* module client
code, which is apparently not good, because data systems don't reflect correct
(current) state at this time.

Either this should be hugely documented and ways of how to solve this shown and
written, or there should be some concept of "priority listeners" or whatever in
filesystems which will allow data systems to be consistent before user code
starts to ask.
Comment 1 David Simonek 2002-01-10 10:39:06 UTC
CC'ing filesystems maintainer Radek.
Comment 2 rmatous 2002-01-10 11:13:08 UTC
This enhancement should be probably filed against filesystems because
DataSystems have no chance to control a way of firing events from
filesystems. Also take note that FileSystems are independent and can
be used without DataSystems. Probably also TargetMilestone should not
be 3.3.1.
Comment 3 David Simonek 2002-01-10 11:57:51 UTC
ok, I agree. Keep in mind that data systems will have to change as
well if such support will be added to filesystems.
Comment 4 phamernik 2002-01-30 09:50:32 UTC
Changing owner -> Radek Matous.
Comment 5 _ ttran 2002-02-19 16:09:03 UTC
defer to 4.0, architecture issue, should be solved in sync with the
new loaders API
Comment 6 rmatous 2002-07-23 11:21:21 UTC
Questins for new loaders API gurus: do you consider this issue as
necessary ?Is it necessary to mix using FileSystem and DataSystem
together at all? Perhgaps new loaders API and naming could solve this
problem in any way, couldn`t it ?
Comment 7 Jaroslav Tulach 2002-07-24 10:45:40 UTC
This is probably caused by the fact that window system was not able to
use FolderInstance and had to implement it itself. I believe the issue
should be addressed by JNDI+events. 

In order to (partially) solve this issue without major changes, it
should be enough to notify first of all listeners on Repository and
after that those on FileSystems and FileObjects. Because WindowSystem
(and others mostly too) listen on FileObjects and new Data System on
Repository this will turn the DataSystem into "priority listener".

Comment 8 rmatous 2002-08-02 11:43:51 UTC
It would be "nice to have" such feature, but I think P4 is more
appropriate and realistic.
Comment 9 Antonin Nebuzelsky 2008-04-15 17:20:05 UTC
Reassigning to new module owner jskrivanek.
Comment 10 Jiri Skrivanek 2008-10-16 11:48:20 UTC
Probably obsolete.