Community
Participate
Working Groups
When attempting to work with a JSP model in a project with JSF/JSTL facets installed, many errors occur. The errors do not occur when the JSF/JSTL facets are not installed on the project. This can be seen by running WPE (pagedesigner) JUnit tests or by following these steps: 1. Create Dynamic Web Project and use "JavaServer Faces v2.1 Project" configuration preset. 2. Create a JSP file using the "New JSP File (html)" template. 3. Open JSP file with "JSP Editor". 4. Note error dialog and errors in log. eclipse.buildId=I20121214-0730 java.version=1.6.0_21 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86_64 This is a continuation of log file D:\workspace_smoketest_350\.metadata\.bak_0.log Created Time: 2013-01-24 11:08:00.902 Error Thu Jan 24 12:05:33 PST 2013 null java.lang.NullPointerException at org.eclipse.jst.jsp.core.internal.util.FacetModuleCoreSupportDelegate.resolveInReferenced(FacetModuleCoreSupportDelegate.java:149) at org.eclipse.jst.jsp.core.internal.util.FacetModuleCoreSupportDelegate.resolve(FacetModuleCoreSupportDelegate.java:221) at org.eclipse.jst.jsp.core.internal.util.FacetModuleCoreSupport.resolve(FacetModuleCoreSupport.java:174) at org.eclipse.jst.jsp.core.internal.contenttype.DeploymentDescriptorPropertyCache.getWebXMLPath(DeploymentDescriptorPropertyCache.java:940) at org.eclipse.jst.jsp.core.internal.contenttype.DeploymentDescriptorPropertyCache.getCachedDescriptor(DeploymentDescriptorPropertyCache.java:800) at org.eclipse.jst.jsp.core.internal.contenttype.DeploymentDescriptorPropertyCache.getPropertyGroups(DeploymentDescriptorPropertyCache.java:873) at org.eclipse.jst.jsp.core.internal.java.JSPTranslator.translatePreludes(JSPTranslator.java:3240) at org.eclipse.jst.jsp.core.internal.java.JSPTranslator.translate(JSPTranslator.java:1115) at org.eclipse.jst.jsp.core.internal.java.JSPTranslationAdapter.getJSPTranslation(JSPTranslationAdapter.java:152) at org.eclipse.jst.jsp.core.internal.validation.JSPJavaValidator.performValidation(JSPJavaValidator.java:314) at org.eclipse.jst.jsp.core.internal.validation.JSPJavaValidator.validateFile(JSPJavaValidator.java:417) at org.eclipse.jst.jsp.core.internal.validation.JSPValidator.validate(JSPValidator.java:196) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:303) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:262) at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269) at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321) at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258) at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691)
That method was introduced with the fix for bug 398698.
Odd, those methods don't say they can return null.
Pushed and released http://git.eclipse.org/c/sourceediting/webtools.sourceediting.git/commit/?id=2fe11ab8fd8d16e17c628f7596f0821ef576e6f1 and http://git.eclipse.org/c/sourceediting/webtools.sourceediting.tests.git/commit/?id=6845de30a516829a8a04cf4761d08d7ae392502d .
Thanks for watching and responding quickly, Nitin. - Ian
And http://git.eclipse.org/c/sourceediting/webtools.sourceediting.git/commit/?id=1fe88f77f17cd924c7bb21efe19bbbc3cbd5e6ef .