I’ve seen similar behaviour in the past and know of two possible reasons:
- Your build path has somehow changed, leaving out your Node class, or the project providing it has compile errors, or similar. Given your description of the problem, this probably isn’t relevant in your case.
- Some Eclipse screwup. For me, this was always solved by doing a clean build of the project (possibly also any dependent projects) at which point things resolved themselves. You can do this by going to the
Projectmenu and selectingClean. This isn’t a proper solution, but strikes me as quicker than yourNode->DNode->Nodeworkaround.
