Bugzilla – Full Text Bug Listing
| Summary: | Project Properties - Facets - Change Configuration - Receive npe error | ||
|---|---|---|---|
| Product: | [WebTools] Java Server Faces | Reporter: | Jolene Moffitt <jolene.moffitt> |
| Component: | Core | Assignee: | Ian Trimble <ian.trimble> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | manderse, neil.hauge, raghunathan.srinivasan, rosendo, yurykats |
| Version: | 3.3 | ||
| Target Milestone: | 3.3 M7 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Jolene Moffitt
This doesn't appear related to having a JAXB faceted project, so you should be able to reproduce with any faceted project. What is a JAXB project? Is it a Web project? Does it have a WebContent folder? (In reply to comment #2) > What is a JAXB project? Is it a Web project? Does it have a WebContent folder? It's really just a faceted project that only contains a JAXB facet. It can be combined with a Web facet to get Web project content. The stack trace suggests there is no WebContent folder in the project, which implies that this is not a valid Dynamic Web Project to begin with. I don't know why, just throwing it out there. (In reply to comment #4) > The stack trace suggests there is no WebContent folder in the project, which > implies that this is not a valid Dynamic Web Project to begin with. > I don't know why, just throwing it out there. That would probably explain the NPE. : ) I guess we need to figure out why these configurations are available. I was able to reproduce with a JPA project (faceted project with Java and JPA facets). The JAXB facet also has the Java facet, which I didn't mention before. Took another look at this. The Configurations appear to be valid options. All you need is a plain faceted project to reproduce the issue. I encountered this exception first while testing selection of JSF Configurations. java.lang.NullPointerException at org.eclipse.jst.j2ee.project.facet.J2EEModuleFacetInstallDataModelProvider.handleProjectFacetsChanged(J2EEModuleFacetInstallDataModelProvider.java:216) at org.eclipse.jst.j2ee.project.facet.J2EEModuleFacetInstallDataModelProvider.access$0(J2EEModuleFacetInstallDataModelProvider.java:198) at org.eclipse.jst.j2ee.project.facet.J2EEModuleFacetInstallDataModelProvider$2.handleEvent(J2EEModuleFacetInstallDataModelProvider.java:180) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.notifyListeners(FacetedProjectWorkingCopy.java:1752) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.resumeEventNotification(FacetedProjectWorkingCopy.java:1797) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.setSelectedPreset(FacetedProjectWorkingCopy.java:1097) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$8.widgetSelected(ModifyFacetedProjectWizard.java:576) ... Moving this to 3.3 since we are in ramp down for 3.2.3 I just spotted this again and yes, this is reproducible by creating a new faceted project, go to Facet properties and enable/disable the JSF facet. It seems it assumes that it is always called on a dynamic web project and that is not the case when the user is just selecting the facet. org.eclipse.jst.jsf.core.internal.project.facet.JSFFacetInstallDataModelProvider was making some invalid assumptions about the existence of a Java project. Fix submitted at 2011/03/21 04:17PM PDT. (In reply to comment #6) > Took another look at this. The Configurations appear to be valid options. All > you need is a plain faceted project to reproduce the issue. > > I encountered this exception first while testing selection of JSF > Configurations. > > > > java.lang.NullPointerException > at > org.eclipse.jst.j2ee.project.facet.J2EEModuleFacetInstallDataModelProvider.handleProjectFacetsChanged(J2EEModuleFacetInstallDataModelProvider.java:216) > at > org.eclipse.jst.j2ee.project.facet.J2EEModuleFacetInstallDataModelProvider.access$0(J2EEModuleFacetInstallDataModelProvider.java:198) > at > org.eclipse.jst.j2ee.project.facet.J2EEModuleFacetInstallDataModelProvider$2.handleEvent(J2EEModuleFacetInstallDataModelProvider.java:180) > at > org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.notifyListeners(FacetedProjectWorkingCopy.java:1752) > at > org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.resumeEventNotification(FacetedProjectWorkingCopy.java:1797) > at > org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.setSelectedPreset(FacetedProjectWorkingCopy.java:1097) > at > org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$8.widgetSelected(ModifyFacetedProjectWizard.java:576) > ... Regarding comment # 6, a new bugzilla was created: https://bugs.eclipse.org/bugs/show_bug.cgi?id=340689 and a patch was attached with a proposed fix. |