Bugzilla – Full Text Bug Listing
| Summary: | [prefs] Better define behaviour of #nodeExists for project nodes | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | DJ Houghton <dj.houghton> |
| Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | ||
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. |
We need to better define the behaviour of #nodeExists for the nodes in the project scope. Currently we over-ride super-class impl such that the node does exist if the super-class says that it does or if you are at /project and you are asking about a single segment name and that name is the name of a project that exists in the workspace. The impl doesn't work for long paths though since super accesses the cache of children. (e.g. nodeExists("myProject/qualifier/nodeName") Investigate the interaction between #nodeExists and #getChild, #getChildren, and #childnames.