Bug 90500 - [prefs] Better define behaviour of #nodeExists for project nodes
Summary: [prefs] Better define behaviour of #nodeExists for project nodes
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-06 13:51 EDT by DJ Houghton CLA
Modified: 2019-09-06 15:32 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description DJ Houghton CLA 2005-04-06 13:51:36 EDT 
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.
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:32:30 EDT 
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.