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.
Repetitive activation of nodes A, B, A, B,... always does parsing of the activated node, although the file did not change at all.
Situation now alot better. Parsing is still being done, but now parsing is 4x faster and doesn't block AWT anymore, so I believe no caching is needed and bad impact of this bug is gone. Re to Tim: As you already know, blocking was during Navigator's painting, due to complexity and frequency of JMI calls done at that time.
I agree that caching in this case is not needed.