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.
Get an NB 6 daily build. Download and install the UML category from the dev update center. After modules install, the following exception is thrown: java.io.IOException: Top component designpattern could not be loaded, either owning module was disabled, has incompatible version or top components settings file format is broken. at org.netbeans.core.windows.persistence.PersistenceManager.getTopComponentPersistentForID(PersistenceManager.java:497) at org.netbeans.core.windows.persistence.PersistenceManager.getTopComponentForID(PersistenceManager.java:583) at org.netbeans.core.windows.PersistenceHandler.getTopComponentForID(PersistenceHandler.java:392) at org.netbeans.core.windows.PersistenceHandler.topComponentRefConfigAdded(PersistenceHandler.java:768) [catch] at org.netbeans.core.windows.persistence.ModuleChangeHandler$3.run(ModuleChangeHandler.java:331) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:597) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160) at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
I tested on NB 200703251800 build, the initial installation of all uml nbms seems to be fine. This exception happens when NB enables a module that defines a top component through settings file, nothing specific to uml. Try to disable and then re-enable Versioning modules from Module Manager, you'll get the same exception. Re-assign to windows/persistence for further investigation.
Reason is that InstanceDataObject (used by winsys to instantiate TopComponents) does not return InstanceCookie for given TC when asked during module activation ie. creating of TC instance fails. Winsys listens to filesystem events and when some new data appears on filesystem winsys process them. Probably it is done before InstanceDataObject is ready to provide InstanceCookie. But I do not know about any way how to synchronize this ie. how can we know that IDO is ready to provide InstanceCookie.
*** Issue 66373 has been marked as a duplicate of this issue. ***
Sounds like a possible bug in openide/loaders to me - IDO ought to return a valid instance if the module layer has been loaded.
The problem is that IDO and winsys uses FS events and there is no warranty that IDO will process (ie. will provide valid instance) FS event before winsys. Now I tried to reptroduce this with new plugin manager but it does not happen. If anybody will have any way how to reproduce it now please let me know. I tried to install some plugins (modules inside) which contain tc ref but it did not happen. The problem can happen even now it just depends on order in which FS events are delivered to listeners.
moving opened issues from TM <= 6.1 to TM=Dev
there were some changes in the sfs filesystem (mainly ergonomics related), please reopen if still reproducible in recent builds, thanks