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 87593 - Classpath config for codegen to resolve not-fully-qualified types
Summary: Classpath config for codegen to resolve not-fully-qualified types
Status: NEW
Alias: None
Product: uml
Classification: Unclassified
Component: Code Generation (show other bugs)
Version: 5.x
Hardware: PC All
: P2 blocker (vote)
Assignee: issues@uml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-20 02:30 UTC by Craig Conover
Modified: 2007-07-03 23:07 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
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 Craig Conover 2006-10-20 02:30:36 UTC 
- On an operation element, add IOException to its Raised Exceptions property.
- Generate Code
- The operation will have the "throws IOException" added but it won't compile
because the import for IOException is not generated.
Comment 1 Peter Lam 2007-03-20 20:21:18 UTC 
low use case not currently impacting our installed user base.
Comment 2 Viktor Lapitski 2007-07-03 23:07:56 UTC 
adding of fully qualified java.io.IOException to 
the Raised Exceptions property would make generated code correct.

Automated resolving of IOException into something 
like java.io.IOException would mean searching through the class 
path like for example Java Editor for import fixing. It would 
require some notion of classpath config to be associated 
with the UML project (or more specifically it may be 
a configuration item for a codegen engine that 
is being used, supposing that we'll have more than one 
pluggable/configurable codegen engine(s))