|
|
|
The Model-Driven System Builder
|
|
JeeWiz Architect's Guide
|
|
|
|
Contents >
4. Meta-Models And Template Directories
|
|
|
4.1 Basics
4.1.1 Naming Conventions
|
In the specification of a meta-model,
it is recommended that you use separate XML files for each meta-class and meta-factor, using the '-' style name.
For example, to define a 'reference type' meta-class, define it in a file 'reference-type.xml' in the meta-model's specification directory.
You will also need a separate assembly.xml for the <meta-model> element.
4.1.2 Names
|
There are a number of 'names' for a meta-model you need to specify:
- The meta-model name attribute. This is defined in the <meta-model> element.
This is used for inter-meta-model references in the meta-model specification. It is not used in the renderings.
- The descriptive name - this should be capitalised because it is used as the title on documentation
- The directory in which the meta-model is stored.
All the JeeWiz product meta-models are in directories under jeewiz/resouces.
Not all such directories have meta-models - some are rendering overlays only.
A meta-model {m} will be stored under jeewiz/resources/{m}/specification,
and this directory must have an assembly.xml file in it, whose root element is the 'meta-model' element in the meta-model specification.
4.1.3 Directory Structure
|
As noted above, the meta-models are typically stored under jeewiz/resources, but they can be in any directory.
Copyright (c) 2001-2008 New Technology/enterprise Ltd.
| |
