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 24790 - Logical Metamodel design
Summary: Logical Metamodel design
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Linux
: P1 blocker (vote)
Assignee: Pavel Flaska
URL:
Keywords:
Depends on:
Blocks: 24792 24800 24802
  Show dependency tree
 
Reported: 2002-06-14 18:03 UTC by Pavel Flaska
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Flaska 2002-06-14 18:03:25 UTC
Create a metamodel layer on top of the physical
metamodel, which will operate with the project
context and will contain associations, rather than
symbolic references between individual elements.
The metamodel should contain provisions to capture
and/or track unresolved referencies, too. The
metamodel should contain only a minimal data,
rather it should proxy to and associate elements
from the Physical metamodel.
Comment 1 Pavel Flaska 2002-08-27 15:13:14 UTC
There won't be special logical metamodel. It will be part of the
Project metamodel. See diagram
http://java.netbeans.org/models/java/img/Project.png.

You can see three derived associations pointing to the Physical
metamodel - HasResources, BelongsTo and Packages. They contain sum of
all links for all codebases in classpath.
For JavaClass, you can use methods in Classpath element. You can find
JavaInterface implementors, JavaClass interfaces, superclasses etc.
Similiar methods should be implemented in JavaClass element. (We will
use Project instance as a paramater.) See diagram for details.
Comment 2 Tomas Hurka 2002-09-18 15:43:39 UTC
Done in branch meta_2