Eeplat metadata-driven execution engine

Eeplat adopts the metadata-driven core idea. Therefore, the most important thing about eeplat is its complete metadata model system and efficient and flexible parsing execution engine. The execution engine of eeplat parses metadata based on the meta-model and explains the operation to form the final business system.

Based on the idea of model-driven architecture (MDA), eeplat further proposes the concept of "model-driven software". The complete metadata formed by the eeplat configuration definition can be directly executed. The metadata-driven execution process reduces the intermediate model conversion level than the standard MDA level, and can be directly driven by the execution engine to generate the final software system. In theory, eeplat can provide multiple technical platforms (Java ,. net, PHP, Ruby, etc.) execution engine, can be widely run on a variety of technical platforms and operating systems, such as Windows, Linux, Unix (HP/sunsolias/ibm aix) and so on. At present, eeplat mainly develops J2EE-based execution engines. During the development of eeplat, I once developed the. NET execution engine, and then focused on the J2EE execution engine due to the limited applicability and company resources.

The eeplat execution engine adopts a micro-kernel and plug-in architecture. The microkernel is responsible for the relationship between models and message transmission. Plug-ins include storage, query, UI, logic, and process. Plug-ins can be customized and replaced. The UI engine is implemented based on hmvc and controller registry. The Controller Registry has a device relationship and can be mapped between different devices. It supports pcbrowse and smart terminal interface (such as mobile phone and pad) display. At the same time, considering the versatility of the system in Android, Apple and other mobile terminal operating systems, the HTML5 + JS solution is mainly used to achieve cross-platform features.

 

That is, a configuration can generate two interfaces, PC and mobile, based on the same metadata. As shown in the following figure, the first is the PC interface, and the last three are the effects of the UI displayed under the Mobile Interface Engine. Because the device size is different, one interface in the PC is mapped to three mobile interfaces.

 

Www. eeplat. comqq group: 105867861 (enter eeplat2014 for verification)