Bug 236831 - NullPointerException at org.netbeans.modules.web.jsf.editor.index.JsfIndex.<init>
NullPointerException at org.netbeans.modules.web.jsf.editor.index.JsfIndex.<i...
Status: RESOLVED FIXED
Product: javaee
Classification: Unclassified
Component: JSF Editor
7.4
All All
: P3 (vote)
: 8.0
Assigned To: Martin Fousek
issues@javaee
EXCEPTIONS_REPORT
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-07 12:46 UTC by Michel Graciano
Modified: 2013-10-08 06:18 UTC (History)
0 users

See Also:
Issue Type: DEFECT
:


Attachments
stacktrace (2.67 KB, text/plain)
2013-10-07 12:46 UTC, Michel Graciano
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Graciano 2013-10-07 12:46:20 UTC
This bug was originally marked as duplicate of bug 194841, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.4 RC2 (Build 201309252201)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.0-b56, Java(TM) SE Runtime Environment, 1.7.0_40-b43
OS: Linux

User Comments:
hmichel: Just created a Java project, and during the opening of its main class I faced this issue. The main class name was lombok (without any package)




Stacktrace: 
java.lang.NullPointerException
   at org.netbeans.modules.web.jsf.editor.index.JsfIndex.<init>(JsfIndex.java:87)
   at org.netbeans.modules.web.jsf.editor.index.JsfIndex.create(JsfIndex.java:69)
   at org.netbeans.modules.web.jsf.editor.JsfSupportImpl.getIndex(JsfSupportImpl.java:252)
   at org.netbeans.modules.web.jsf.editor.facelets.FaceletsLibrarySupport.checkLibraryDescriptorsUpToDate(FaceletsLibrarySupport.java:205)
   at org.netbeans.modules.web.jsf.editor.facelets.FaceletsLibrarySupport.indexedContentPossiblyChanged(FaceletsLibrarySupport.java:181)
   at org.netbeans.modules.web.jsf.editor.JsfSupportImpl.indexedContentPossiblyChanged(JsfSupportImpl.java:246)
Comment 1 Michel Graciano 2013-10-07 12:46:22 UTC
Created attachment 140854 [details]
stacktrace
Comment 2 Michel Graciano 2013-10-07 12:56:55 UTC
When it happened I had 2 Maven projects (one Web and other is the POM project), and I had one HTML5 project too, which just points to the Maven Web project. None of this projects have any JSF file btw.
Comment 3 Martin Fousek 2013-10-08 06:18:08 UTC
(In reply to Michel Graciano from comment #2)
> When it happened I had 2 Maven projects (one Web and other is the POM
> project), and I had one HTML5 project too, which just points to the Maven
> Web project. None of this projects have any JSF file btw.

That's some kind of obscure situation where project's execution classpath has to be null. In any case no such NPE should appear anymore. Fixed in web-main #df5a7aef4372.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo