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.
If I ask Lookup for all instances of MIMEResolver.class, I'll get all entries duplicated. i.e.: Collection all = result.allInstances(); HashSet uniq = new HashSet(all) all.size() == 2* uniq.size() Not sure if it isn't problem of the lookup, reassing on your decision
It seems like a problem in lookup as there are returned same intances: MIMEResolverImpl.Impl[Services/MIMEResolver/org-apache-tools-ant-module-mime-resolver.xml, [Lorg.netbeans.core.filesystems.MIMEResolverImpl$FileElement;@4d518c]:2973611 MIMEResolverImpl.Impl[Services/MIMEResolver/org-netbeans-modules-jarpackager-mime-resolver.xml, [Lorg.netbeans.core.filesystems.MIMEResolverImpl$FileElement;@1fb328]:5468147 MIMEResolverImpl.Impl[Services/MIMEResolver/org-netbeans-modules-scripting-mime-resolver.xml, [Lorg.netbeans.core.filesystems.MIMEResolverImpl$FileElement;@2b37e2]:6417127 MIMEResolverImpl.Impl[Services/MIMEResolver/org-apache-tools-ant-module-mime-resolver.xml, [Lorg.netbeans.core.filesystems.MIMEResolverImpl$FileElement;@4d518c]:2973611 MIMEResolverImpl.Impl[Services/MIMEResolver/org-netbeans-modules-jarpackager-mime-resolver.xml, [Lorg.netbeans.core.filesystems.MIMEResolverImpl$FileElement;@1fb328]:5468147 MIMEResolverImpl.Impl[Services/MIMEResolver/org-netbeans-modules-scripting-mime-resolver.xml, [Lorg.netbeans.core.filesystems.MIMEResolverImpl$FileElement;@2b37e2]:6417127
BTW: It seems that fixing this could speed up recognition of DataObject by about 10%
I have listed all items and it seems that they are really registered twice. Find out why: item: SL[/IDEConfiguration/System/MIMEResolver/org-apache-tools-ant-module-mime-resolver item: SL[/IDEConfiguration/System/MIMEResolver/org-netbeans-modules-jarpackager-mime-resolver item: SL[/IDEConfiguration/System/MIMEResolver/org-netbeans-modules-scripting-mime-resolver item: SL[/MIMEResolver/org-apache-tools-ant-module-mime-resolver item: SL[/MIMEResolver/org-netbeans-modules-jarpackager-mime-resolver item: SL[/MIMEResolver/org-netbeans-modules-scripting-mime-resolver
More likely bug in the way how settings and their UI is organized on the XML layer.
Strange. MIME Resolvers are defined absolutely same way as e.g. compiler types in the xml layer. But comp. types are listed just once in the lookup result! Me and Vita are going to separate ui from Services folder but IMO the Lookup behavior should be consistent for shadows.
/Services/IDEConfiguration/System/MIMEResolver/ is a DataShadow to /Services/MIMEResolver The fix should be based on storing the links somewhere else - /UI/ folder, etc...
Increased priority to P1. Category locations must be changed before beta releasing.
for more info about proposed solution and impact on modules, see: http://www.netbeans.org/servlets/ReadMsg?msgId=164880&listName=nbdev
Separating settings UI presentation from the lookup storage fixed this problem. Lookup query for MIMEResolver.class returns unique instances of resolvers. Please verify. [9 Oct 2001] Fixed in main trunk.
Verifying against latest CVS trunk sources as of 200110091000
Resolved for 3.4.x or earlier, no new info since then -> closing.