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 88602 - java.awt.event.Action is RE'ed into an Interface element instead of interface datatype
Summary: java.awt.event.Action is RE'ed into an Interface element instead of interface...
Status: NEW
Alias: None
Product: uml
Classification: Unclassified
Component: Reverse Engineering (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@uml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-03 13:33 UTC by Alexandr Scherbatiy
Modified: 2009-05-25 21:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
'MyFrame' java class (1.42 KB, text/plain)
2006-11-03 13:34 UTC, Alexandr Scherbatiy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandr Scherbatiy 2006-11-03 13:33:20 UTC
Steps to reproduce:

- Reverse Engineer the attached 'MyFrame' java class into UML project
- Generate code for the UML project
- Go to the generated java project

 The project contains mistakenly generated 'ActionListener' interface 
  under 'java.awt.event' package
  --------------------------------------------------------------
  package java.awt.event;

  public interface ActionListener {
  }
  --------------------------------------------------------------
Comment 1 Alexandr Scherbatiy 2006-11-03 13:34:31 UTC
Created attachment 35766 [details]
'MyFrame' java class
Comment 2 Peter Lam 2007-03-20 20:12:00 UTC
low use case not currently impacting our installed user base.
Comment 3 Craig Conover 2007-06-26 03:48:43 UTC
new code gen module; problem no longer exists
Comment 4 Alexandr Scherbatiy 2007-06-26 12:44:41 UTC
The problem still exists in netbeans-hudson-trunk-1189-full.zip
Just follow the described steps.
Comment 5 Craig Conover 2007-07-18 18:46:03 UTC
I see now. This is really a RE problem. The Code Gen process sees an Action interface in the project and generates code
for it. The RE process should have created an interface datatype instead, and the Code Gen process would/should ignore it.

Changing subcomponent to reverse engineering.
Comment 6 Craig Conover 2007-07-18 20:00:25 UTC
Reworded Summary to indicate issue is in RE process, not CG process.
Comment 7 George Vasick 2007-09-21 19:50:04 UTC
Proper solution requires correct resolution of types, i.e. javac parsing.  In the short term, we map the type to
datatype.  Datatypes behave more like class than interface types.  We don't have a good solution in the current framework.

Users should avoid code generation on java packages in the mean time.
Comment 8 George Vasick 2008-01-15 22:04:56 UTC
Reviewed and approved for waiver by UML -iteam.
Comment 9 Peter Lam 2008-05-20 23:07:29 UTC
still exists in 6.5
Comment 10 George Vasick 2008-06-10 17:11:44 UTC
Removing obsolete assignments.  Bugs will be reassigned for M2.
Comment 11 Sergey Petrov 2008-11-05 12:01:50 UTC
currently there are two solutions to handle this case, user can easily remove extra generated code, or generate code
only on specific packages in uml project.