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 51488 - AssertionError when pressing Enter on a .class node in project explorer
Summary: AssertionError when pressing Enter on a .class node in project explorer
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Daniel Prusa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-13 16:18 UTC by _ ttran
Modified: 2005-01-24 16:30 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ ttran 2004-11-13 16:18:46 UTC
[jdk 1.5, IDE built from CVS 2004/11/13, linux]

I just file an issue 51487: .class files were
checked in CVS mistakenly.  But here is another one:

The focus is in the Project explorer, I browse and
select a .class node.  Context menu on that node
doesn't show "Open" nor "Edit" but I press Enter
and get this exception

java.lang.AssertionError
	at
org.openide.actions.FileSystemAction.actionPerformed(FileSystemAction.java:201)
	at
org.openide.explorer.view.TreeView$PopupSupport.actionPerformed(TreeView.java:1180)
	at
javax.swing.JComponent$ActionStandin.actionPerformed(JComponent.java:3194)
	at
javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1571)
	at
javax.swing.JComponent.processKeyBinding(JComponent.java:2730)
	at
javax.swing.JComponent.processKeyBindings(JComponent.java:2765)
	at
javax.swing.JComponent.processKeyEvent(JComponent.java:2693)
	at
java.awt.Component.processEvent(Component.java:5265)
	at
java.awt.Container.processEvent(Container.java:1966)
	at
java.awt.Component.dispatchEventImpl(Component.java:3955)
	at
java.awt.Container.dispatchEventImpl(Container.java:2024)
	at
java.awt.Component.dispatchEvent(Component.java:3803)
	at
java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1810)
	at
java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:668)
	at
java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:916)
	at
java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:794)
	at
java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:632)
	at
java.awt.Component.dispatchEventImpl(Component.java:3841)
	at
java.awt.Container.dispatchEventImpl(Container.java:2024)
	at
java.awt.Window.dispatchEventImpl(Window.java:1766)
	at
java.awt.Component.dispatchEvent(Component.java:3803)
	at
java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
[catch] at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:234)
	at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
	at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
	at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
	at
java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

-----
Please also check NB 4.0 if the same bug is there.
 Can be a candidate for a 4.0.1 update
Comment 1 Jiri Rechtacek 2004-11-15 15:58:39 UTC
[dev 2004/11/15] Easy reproducible on any class node, in Projects view
and in Files view. Class node wrongly returns default action.
Luckily, it is not reproducible in NB4.0 (built from sources 2004/11/10).
Comment 2 Jiri Rechtacek 2004-11-15 17:33:42 UTC
Worse, AssertionError also shown in NB4.0 if assertions are enabled,
of course.
Comment 3 Jiri Rechtacek 2004-11-22 12:59:23 UTC
Default action is a responsibility of clazz module. After removing the
action Customize as ... then the filesystem action become default
action of class node. Should be removed from class node's actions.
Comment 4 Martin Matula 2004-11-23 13:17:05 UTC
Dan, please look at it.
Comment 5 Daniel Prusa 2005-01-24 16:30:39 UTC
I am also able to reproduce the assertion error in NB4.0, however, the
problem seems to be fixed in current dev builds, since Open action is
available and it is invoked when Enter is pressed on a class node.