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 118169 - IllegalStateException occurs in message.log file when create a WebModule project
Summary: IllegalStateException occurs in message.log file when create a WebModule project
Status: RESOLVED DUPLICATE of bug 117498
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: Winston Prakash
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-09 00:58 UTC by davisn
Modified: 2007-10-12 18:51 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
messages.log (41.71 KB, application/octet-stream)
2007-10-09 00:59 UTC, davisn 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description davisn 2007-10-09 00:58:22 UTC 
IllegalStateException occurs in the message.log file when create a WebModule project with having Visual Java Server
Faces as default

STEPS TO REPRODUCE:
1. Install Netbean nightly build 10/08/2007 with glassfish V2
2. Create a Web Module project with selecting Visual Java Server Faces for default component
BUG:
    java.lang.IllegalStateException: You are trying to access file:  from the default package. Please see
http://www.netbeans.org/download/dev/javadoc/org-openide-modules/org/openide/modules/doc-files/classpath.html#defau
        at org.netbeans.ProxyClassLoader.printDefaultPackageWarning(ProxyClassLoader.java:500)
        at org.netbeans.ProxyClassLoader.getResource(ProxyClassLoader.java:280)
        at java.lang.ClassLoader.getResource(ClassLoader.java:972)
        at java.lang.ClassLoader.getResource(ClassLoader.java:972)
        at com.sun.webui.jsf.theme.JSFThemeContext.getResourcePath(JSFThemeContext.java:148)
        at com.sun.webui.jsf.util.JavaScriptUtilities.getThemeJavaScript(JavaScriptUtilities.java:515)
        at com.sun.webui.jsf.util.JavaScriptUtilities.getDojoConfig(JavaScriptUtilities.java:131)
        at com.sun.webui.jsf.renderkit.html.HeadRenderer.renderAttributes(HeadRenderer.java:134)
        at com.sun.webui.jsf.renderkit.html.AbstractRenderer.encodeBegin(AbstractRenderer.java:156)
        at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:785)
        at org.netbeans.modules.visualweb.insync.faces.FacesPageUnit.renderBean(FacesPageUnit.java:1289)
        at org.netbeans.modules.visualweb.insync.faces.FacesPageUnit.renderNode(FacesPageUnit.java:1545)
        at org.netbeans.modules.visualweb.insync.faces.FacesPageUnit.renderBean(FacesPageUnit.java:1337)
        at org.netbeans.modules.visualweb.insync.faces.FacesPageUnit.renderNode(FacesPageUnit.java:1545)
        at org.netbeans.modules.visualweb.insync.faces.FacesPageUnit.renderBean(FacesPageUnit.java:1337)
Comment 1 davisn 2007-10-09 00:59:05 UTC 
Created attachment 50454 [details]
messages.log
Comment 2 David Konecny 2007-10-09 08:13:51 UTC 
I followed your steps and could not reproduce this exception. Has is happened just after you created new project?

Anyway, looking at the exception the file which is being accessed is blank string. That's strange but let's put it aside
for now. If you follow the link in exception you will learn that "Loading classes from the default (root) package is
disabled. You can load resources from that package but a warning is printed. ..." So in this case it is just
informational exception which is not causing any harm.

So, how to reproduce this?
Comment 3 David Konecny 2007-10-11 09:18:50 UTC 
Feel free to reopen and provide more info on how to reproduce, how often it happens to you, does it happen only on one
project or on all of them, on particular JSF file or on all of them, ...

As I said earlier, exception in this case is harmless, but knowing the cause of it I could get rid of it completelly.

Thx, David.
Comment 4 David Konecny 2007-10-12 12:57:36 UTC 
I'm able to reproduce it by following original reporters instruction. The problem must be in woodstock components trying
to access ??? something. It happens anytime you open a visual jsp file.
Comment 5 Peter Zavadsky 2007-10-12 17:09:54 UTC 
This belongs to the theme jar. Passing to components.
Comment 6 Dongmei Cao 2007-10-12 18:51:04 UTC 

*** This issue has been marked as a duplicate of 117498 ***