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 73015 - DataShadow.ShadowNode Supplies Incorrect Lookup
Summary: DataShadow.ShadowNode Supplies Incorrect Lookup
Alias: None
Product: platform
Classification: Unclassified
Component: Data Systems (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jaroslav Tulach
Depends on:
Blocks: 62707
  Show dependency tree
Reported: 2006-02-25 00:30 UTC by tomwheeler
Modified: 2008-12-22 17:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Fix of the problem, but not compatible fix, will need a lot of tuning (8.81 KB, patch)
2006-06-19 16:51 UTC, Jaroslav Tulach
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description tomwheeler 2006-02-25 00:30:17 UTC
Per the thread here:

I can do a lookup on a node and successfully get back an arbitrary object that
was stored there (e.g. in the performAction(Node[]) method of CookieAction). 
However, this fails in many cases where the node is actually a
DataShadow.ShadowNode instead of the original node.

It seems that the DataShadow.ShadowNode lookup only returns itself, the
DataShadow it represents and objects implementing Node.Cookie.  No other objects
are returned from the lookup.
Comment 1 Jaroslav Tulach 2006-04-10 12:13:10 UTC
True. This is the result of ShadowNode extending FilterNode and overwriting 
its getCookie, then the filternode's lookup does needs to delegate to the 
getCookie method and as such all other objects from original's node lookup get 

The most of all I would rather close this issue, but I am afraid it blocks 
issue 62707, so I am at least adding this as a blocker.
Comment 2 Jaroslav Tulach 2006-06-19 16:51:04 UTC
Created attachment 31159 [details]
Fix of the problem, but not compatible fix, will need a lot of tuning
Comment 3 Jaroslav Tulach 2006-10-30 17:00:21 UTC
If the latest patch from issue 73015 is fixed, this issue will get fixed as 
well. At least it seems so:
Comment 4 Jaroslav Tulach 2006-11-06 08:25:28 UTC
Fixed as part of issue 62707:

Checking in 
initial revision: 1.1