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.
Summary: | [41cat] NPE after using hyperlink on CC window | ||
---|---|---|---|
Product: | javaee | Reporter: | cezariusz <cezariusz> |
Component: | JSP | Assignee: | Petr Pisl <ppisl> |
Status: | CLOSED FIXED | ||
Severity: | blocker | Keywords: | JDK_SPECIFIC |
Priority: | P2 | ||
Version: | 4.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
messages.log
Where to click NPE thrown when clicking "Deprecated" in help window. |
Description
cezariusz
2005-03-16 08:42:04 UTC
Created attachment 20873 [details]
messages.log
BTW: CC should be invoked on position | -- it's <center> tag from HTML help. <cen|t I'm not able to reproduce it on WinXP, JDK 1.5.0_02 in JSP nor in HTML. Hi Cezariusz, the NPE is from obtaining the font size. The default font size was changed a few days ago so I expect, that it could be there a connection with this. Did you try new build with old userdir? Or did you set up a font size before for something? I'm asking, because I'm not able to reproduce it as well. 1. It also happens with clean userdir (100% reproducible here) 2. I didn't change any font sizes, just installed the new daily build over previous one. Created attachment 20881 [details]
Where to click
I'm not stil able to reproduce it on my Linux mashine. Karel could you try it on win XP? I can't reproduce it either in #200503061900 but with JDK 1.5.0_02 on Windows XP. I wonder if you could test it with Java 5 Update 2 and I will do the same with your Java 5 Update 1. I would also be curious if you use proxy and firewall. Any info is appreciated. I have received only one NPE during my testing but it's not the same. See attachment. Created attachment 20891 [details]
NPE thrown when clicking "Deprecated" in help window.
According to log file you run on 1.5.0-b64 and not 1.5.0_01. I can reproduce it on this JDK version and it works well on my JDK1.5.0_02-b07. I am not sure what is right resolution but it is probably not so important. Radim, you are right. Thanks for the notice this. So it's look like a bug in the swing. You're right, there was JDK 5.0 on that machine. After installing Update 2 the exception no longer occurs. Sorry for the confusion. |