Community
Participate
Working Groups
Driver: WTP 3.0 12/20 driver When a user does not choose an initial project, creating a top-down Web service result in an NPE: IWAB0014E Unexpected exception occurred. java.lang.NullPointerException at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl.create(FacetedProjectFrameworkImpl.java:659) at org.eclipse.wst.common.project.facet.core.ProjectFacetsManager.create(ProjectFacetsManager.java:344) at org.eclipse.jst.ws.internal.consumption.common.FacetUtils.isJavaProject(FacetUtils.java:1357) at org.eclipse.jst.ws.internal.creation.ui.extension.PreServiceDevelopCommand.execute(PreServiceDevelopCommand.java:180) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419) This problem also always shows up when running the Web service Ant scenario as well.
This bug was introduced when fixing bug 200193. A check for initialProject equals null has been added to PreServiceDevelopCommand and PreServiceAssembleCommand. The fix has been committed and released to HEAD as v200712202051.
would it make sense if instead of requiring the caller to check for null before calling, to just return false immediately, if the argument was null? Just wondering.
Verified by Kelvin on 12/21 WTP 3.0 driver. Bug 213730 has been opened to have FacetUtils.isJavaProject() properly guard against null input parameter.