This issue was already filed before, so this is a duplicate. Passing to insync (setting the context classloader, which
should assure this NPE won't happen).
But here are more info:
This issue caused the themes of the components to be gone. Also Krys, is trying to get reproducible case.
Note, this happens in trunk. (Exceptions reporter is defaulting to 6.0)
Here is build info:
: NetBeans IDE Dev (Build 20080124125258)
Java: 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19
System: Windows XP version 5.1
I have found a simple reproducible cases that outputs about multiple
NPE at javax.faces.component.UIComponentBase.getRenderer, hence making this a P2.
1. Restart ide and create a vw ee5 project
2. Drop a textfield component
3. Create a second vw ee5 project and also drop a textfield
4. File -> close "webappXX" that second project.
5. The first project is now fronted, click on Page1 tab of first project
6. Then drag and drop another component from palette to designer
> will get 3 or more NPE's (depending on the component dropped)
I've reproduced this at least 5 times in case you have any problems reproducing.
Looks like the facesContext.release() call introduced in the FacesContainer.destroy() for a memory leak fix may have
exposed this. The right fix may be to add a new method in FacesContainer which for wraps the
javax.faces.component.UIComponentBase.getRendersChildren() and takes care of setting up the FacesContext etc. That is
the method that should be used by Designer code.
update: trunk NetBeans IDE Dev (Build 200801271318) with reverted fix. The
NPE's are gone as a result of the given scenario, but further testing, i.e a third project
created and closed show the same loss of theme in designer. No NPEs however.
The base issue however exists in 6.1M1 and we need a better workaround than restart
of the IDE: refresh designer does not help.