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.
because current impl is DataObjectEncodingQueryImplementation that goes through getLookup() to find impl. This means that we need to get node of DO before we get encoding in most of cases. This is probably a big problem if we want to use this in searches and similar acivities.
-> tzezula
It only goes through DataNode if DataObject.getLookup is not overridden. The default impl is not just slow, it is quite deadlock-prone, especially in combination with FEQ (as I have found the hard way); every DO subclass in the IDE should be fixed to override getLookup, I think. I already fixed AntProjectDataObject after getting a couple of deadlocks. apisupport overrides it for newly created DO subclasses. I would suggest that the default impl log a warning (once per subclass) to remind people about it.
moving opened issues from TM <= 6.1 to TM=Dev
still TM=6.5?
If I understand everything correctly, if all DOs would override getLookup reasonably, all should be OK. In issue #146377 Jarda wrote: "we shall fix all data objects we have under our control, e.g. in the NetBeans IDE" (we shall fix all DOs to override getLookup reasonably). Jarda, please make sure this happens. Thanks.
>If I understand everything correctly, if all DOs would override getLookup reasonably, all should be OK. Right
Anyway Jarda is an owner of FEQ from the NB 6.1
Jarda is not owner of FEQ. At most core team is owner of project/queries, but I no longer work in core exclusively. Anyway Andrei managed to fix issue 147492 and as such there are no longer any DataObjects not using own lookup. I guess this issue can be marked as fixed.
Right, Andrei's patch fixes this issue.