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 20041 - Suggest declaring MOF package name as constant in MDR
Summary: Suggest declaring MOF package name as constant in MDR
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: Martin Matula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-01 13:32 UTC by Svata Dedic
Modified: 2004-08-13 12:11 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 Svata Dedic 2002-02-01 13:32:34 UTC 
I noticed that all modules, which currently use MDR have their own constant for
the name of MOF package extent. I suggest to declare such name as a public
static final constant in MDR module.
I also suggest that there's an utility method, which would acquire/create the
MOF metamodel package extent (with the above well-known name) for convenience of
MDR users.
Comment 1 Martin Matula 2002-02-01 16:25:29 UTC 
What is a use-case for such a constant? Note that MDRepository
declares method createPackageInstance(String) that creates instance of
MOF model. Is there other need for knowing the name of MOF package
than just for creating instance of it?
Comment 2 Martin Matula 2004-06-20 11:43:29 UTC 
There is a createExtent method that takes only one parameter and
creates an instance of MOF. This should be enough and the constant
should not be needed.