| Introduction | Applications | Project Tasks | Publications | Related Technologies |
| Project Tasks: | Asset Language | ADL Compiler | COCoMa System Architecture | Modeling Tools |
|
This section lists the subprojects in which parts of the COCoMa environment are being built. ADL, AQL, AML Grammar... Semantics... The ADL compiler creates a COCoMaS from a user's asset definitions. In contrast to traditional compilers the compiler for asset definitions constitutes a framework. It controls the generation of the various modules of a COCoMaS. Generators are developed using the compiler framwork. Like a traditional compiler it is divided into frontend and backend. The frontend includes parsing and checking the asset definitions. The backend consists of module generators which generate the modules of a COCoMaS as described in the architecture documentation. Different backend configurations can be maintained to create different COCoMa systems. There is one API generator which creates the uniform API of all modules. Module generators build implementations of this API. The compiler framework is provided in Java.
There are two noteworthy contributions in the frontend: The ADL Grammar. The grammer describes the syntax of the asset language (definition, query, and manipulation language). It is written for the ANTLR parser generator which is used for the asset compiler.
Intermediate Asset Model. The parser produces an intermediate model of an asset definition file. This intermediate representation is passed to the generators.
The compiler backend mainly consists of generators. There is one API generator which defines the Java interfaces which all generated modules have to implement. There are generators for the various types of modules: client modules, adaptation modules, coordination modules, distribution modules, and server modules. Look at the generator skeleton to get started with generator development. API Generator. All modules follow a uniform API. This is generated by the API generator.
So far, there are two generators being under construction:
Proposals for further client module generators are: Client module generator for relational databases. SQL (JDBC).
Client module generator for XML databases. XML Schema.
Client module generator for the CMS of CoreMedia. The client module generator for the CMS of CoreMedia creates a module which stores assets in the repository of that platform.
Client module generator for the infoAsset Broker. The generator for client modules for the Broker of infoAsset creates a module which maps assets to ones in the notion of assets used in that platform.
Client module generator for email. POP SMTP IMAP WebDAV.
Client module generator for MS Exchange. SyncML.
Currently, two generators for service interfaces are under development: Web Services Interface. This generator creates descriptions of the operations of a COCoMas in the Web Services Description Language (WSDL). This includes the standard operations (
GUI Engine. Open dynamic content management requires dynamically adaptable UIs. Like the domain model the presentation of assets has to be user-definable. To achieve this, we use assets to model the UI realm. It consists of two domains: one for (logical) UI components and one for presentation technologies.
systems, components, modules, ... Tools which help in creating asset models are under investigation: An Eclipse Plug-in for the Asset Language As a development tool to create COCoMaS there is a plug-in for the Eclipse tooling platform. It integrates the asset compiler and uses existing plug-ins which handle the files generated by the asset compiler.
|