This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 108569 - Designer view not opening throwing NullPointerException
Summary: Designer view not opening throwing NullPointerException
Status: REOPENED
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: _ sandipchitale
URL:
Keywords:
: 106209 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-06-30 11:57 UTC by akbani
Modified: 2007-10-24 21:51 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments
IDE Log File (102.30 KB, application/octet-stream)
2007-06-30 11:59 UTC, akbani
Details
JSP Page causing the error (1.18 KB, application/octet-stream)
2007-06-30 12:20 UTC, akbani
Details
Code file corresponding to the JSP causing error (5.96 KB, application/octet-stream)
2007-07-10 12:31 UTC, akbani
Details

Note You need to log in before you can comment on or make changes to this bug.
Description akbani 2007-06-30 11:57:38 UTC
Trying to open a web page throws a NullPointerException

If this error occurs once, i am unable to open any other page for the project
Comment 1 akbani 2007-06-30 11:59:01 UTC
Created attachment 44595 [details]
IDE Log File
Comment 2 akbani 2007-06-30 12:19:27 UTC
I was able to get rid of the error by deleting the file that seemed to cause the issue, its a "Visual Web JSP" file 
which i edited to use framesets. 
Comment 3 akbani 2007-06-30 12:20:36 UTC
Created attachment 44596 [details]
JSP Page causing the error
Comment 4 Peter Zavadsky 2007-07-02 18:14:25 UTC
The NPE is in insync (see the attached log). Passing there.
Comment 5 _ sandipchitale 2007-07-02 19:36:45 UTC
The NPE from Insync seems to be coming as a result of mismatch between the JSF page and the backing bean Java file. 
Can you please attache the .java file that corresponds to the JSF page or even better the project itself. Reopen the 
issue after you supply that information.
Comment 6 _ sandipchitale 2007-07-02 19:42:58 UTC
Additional note:

When you manually replaced the <ui:body .../> tag with the <frameset .../> from the JSP page, did you also remove the 
corresponding getters and setters in the backing bean .java file for all the tags that were removed. If not, that can 
cause the NPE.

Currently this cleanup is not supported by the tool :(
Comment 7 akbani 2007-07-10 12:30:15 UTC
Sorry for the late feedback.

yes, i commented the code for both the form and body tags.

Its not just that the page was not working, the major problem is that all pages in that project stopped opening in
visual designer , even new ones. If some error is caused due to jsp/code mismatch, the error should be localized to the
file itself.
Comment 8 akbani 2007-07-10 12:31:27 UTC
Created attachment 44873 [details]
Code file corresponding to the JSP causing error
Comment 9 _ sandipchitale 2007-10-24 21:42:25 UTC
Visually designed JSF pages are not supported. Converting this to enhancement. We may support it in future release.

A solution for you is to use a simple jsp page with a frameset in it. e.g.

<%-- 
    Document   : Frames
    Created on : 
    Author     : 
--%>

<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
   "http://www.w3.org/TR/html4/loose.dtd">

<html>
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
        <title>JSP Page</title>
    </head>
    <frameset rows="74,457" NORESIZE="true" FRAMEBORDER="0" FRAMESPACING="0" BORDER="0">
        <frame name="header" src="faces/Header.jsp" scroll="no"/>
        <frameset cols="179,821" NORESIZE="true" FRAMEBORDER="10" FRAMESPACING="0" BORDER="0">
            <frame name="menu" src="faces/TreeMenu.jsp" scroll="no" valign="top" />
            <frame name="workbench" valign="top"/>
        </frameset>
    </frameset>
</html>
Comment 10 _ sandipchitale 2007-10-24 21:51:24 UTC
*** Issue 106209 has been marked as a duplicate of this issue. ***