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: | Multicast event generation for user-defined Listener limited | ||
|---|---|---|---|
| Product: | java | Reporter: | fleury <fleury> |
| Component: | Beans | Assignee: | issues@java <issues> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
No beans in 6.0 Add Event Source action has not been converted to java.source API yet NetBeans.org Migration: changing resolution from LATER to WONTFIX |
Generating a multicast event, through the "beans pattern" node in the Projects tab, does not work if the Listener interface contains non-object signatures. Example (does not work): interface MyListener extends EventListener { public void actionPerformed(boolean on_off); }; Similar example (that works): interface MyListener extends EventListener { public void actionPerformed(Boolean on_off); }; However, per section 6.4.1 "Event methods with arbitrary argument lists" from the Java Beans spec, this should work. Most dramatically, NetBeans does give no feedback about what it did or did not do. If it is a limitation that is not worth implementing, at least a feedback should tell the user that it did not generate the code for some reason.