Metadata for Openbiz technology development Manual

Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall

Openbiz Application Development Steps

Openbiz is a metadata based framework, so the application development process may be different from the traditional development

· Step 1: Gather requirements

· Step 2: Design the data model, such as: Data structures

· Step 3: Write business objects including data objects and their metadata

· Step 4: Write a user interface that includes forms and views

· Step 5: Write your own custom data, form, or service object if necessary

· Step 6: Optimize metadata and custom code

· Step 7: Test and Debug

Steps 3 and 4 are all about editing XML metadata, and you can edit them with your favorite XML or text editor. Openbiz Cubi also contains a set of tools to help you quickly generate or edit these metadata.

Managing Meta Data

Introducing Meta Data

Openbiz's core idea is that he is a metadata-driven mechanism, what is metadata? Literally, the metadata is a data component that describes the data. It is "data about data." In openbiz the metadata file acts as a configuration file for the Openbiz class. All openbiz core classes are general classes. They are redefined by different metadata, which represent different transactions and relationships. For example, when Studentdo.xml is associated with a Bizdataobj class, the Bizdataobj instance is a "student" object, but when Schooldo.xml is associated with the Bizdataobj class, the Bizdataobj instance becomes a "School" object.

Because openbiz classes are described by metadata, writing metadata files is like implementing a class, so the development of an application is most of the time the work of writing metadata files, instead of programming in the traditional sense. Using metadata to describe an application will give it a clearer logic and design.

What metadata can achieve:

· Describes the properties of an object

· Describe the relationship between objects

· Describes the rendering (display) method for the presentation Layer object

· Validity of descriptive data calibration method

· Describes how users interact on a page

What the source data does not achieve:

· Logic and functionality, this part should be implemented in real program code, and the "Class" attribute enables a metadata binding to any custom object to achieve special logic and functionality.

Meta Data paradigm

Let's look at two simple meta data examples. Userdo.xml represents a user information object, Usernewform.xml represents a form that creates the user information object, and the meaning of two segments of XML metadata can be interpreted in a self explanatory sense.

Data Object Metadata

Userdo.xml (this file can be found in the Cubi/modules/system/do/directory).

Form Object Metadata

Usernewform.xml (this file can be found in the Cubi/modules/system/form/directory).

Managing Meta data with packages

A good application design is usually modular. Openbiz recommends that developers create their own metadata in a directory structure such as app/modules/. This is precisely the standard openbiz Cubi follows. Openbiz source data files can be organized into module names and subdirectory names, as is the concept of packages implemented in Java. For example:

PackageX.PackageY.metaA.xml references the metab.xml in the Modules/packagea/packageb directory