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.
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.
CC'ing filesystems maintainer Radek.
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.
ok, I agree. Keep in mind that data systems will have to change as well if such support will be added to filesystems.
Changing owner -> Radek Matous.
defer to 4.0, architecture issue, should be solved in sync with the new loaders API
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 ?
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".
It would be "nice to have" such feature, but I think P4 is more appropriate and realistic.
Reassigning to new module owner jskrivanek.
Probably obsolete.