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: | Automatically created PrimitiveTypes package is not complete | ||
|---|---|---|---|
| Product: | java | Reporter: | _ briansmith <briansmith> |
| Component: | Unsupported | Assignee: | Daniel Prusa <dprusa> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 3.x | ||
| Hardware: | PC | ||
| OS: | Windows ME/2000 | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
Fixed. |
When the XMI Reader automatically generates the PrimitiveTypes package (from a MOF 1.3 model), I think that is should make sure it generates the javax.jmi.packagePrefix tag for it. Also, instead of including just the datatypes that are actually used by the metamodel, I think it would be better to always include all of them. That is, if the XMI Reader adds the PrimitiveTypes package, it should always add the XMI equivalent of: package PrimitiveTypes { tag "*tag" : javax.jmi.packagePrefix = 'javax.jmi' on PrimitiveTypes primitive type Boolean primitive type Integer primitive type Long primitive type Float primitive type Double primitive type String } Instead of just, e.g.: package PrimitiveTypes { primitive type String primitive type Integer } I think it is too confusing to have a different version of the PrimitiveTypes package for each metamodel (e.g. some without "Boolean", most without "Long", etc.). Martin said "I agree" on dev@mdr.netbeans.org