Metadata model debugging method and device

Abstract

The embodiment of the invention discloses a metadata model debugging method and device, which are used for debugging a metadata model. The method comprises the steps that a debugging management systemreceives target context information sent by an engine working system; the debugging management system performs decompilation on the target context information to obtain target metadata information corresponding to the target context information; and the debugging management system receives the modification of the target metadata information by the user to obtain the modified target metadata information. The problem that model developers need to be assisted by the engine developers to complete problem positioning in engine development and model implementation is solved, and the method has thecapability of dynamically inquiring and operating engine context variables in the execution process.

Description

technical field [0001] The present application relates to the field of software development, in particular to a metadata model debugging method and device thereof. Background technique [0002] Model-Driven Development (MDD) is a way of software development. Generally speaking, there are two ways to realize model driving: 1. Compile the model into code through automatic tools and execute the code; 2. Drive through metadata, the metadata information predefined by the business engine, according to the metadata information To implement the corresponding business model, the business engine can directly execute the imported business model without generating temporary code during the process. [0003] In the field of communications, operators can quickly generate new services in a metadata-driven manner, import service models into the engine, and execute them, that is, they have the function of developing codes. But for debugging and locating problems, because the metadata-drive...

AI Technical Summary

Problems solved by technology

[0004] However, since the developers of the engine and the model are usually not in the same batch, and the debug logs inevitably reveal the details of the implementation of the back-end engine, the developer of the model often needs the assistance of the developer of the engine to complete the location of the problem

In addition, since the debug log is the output of the engine after execution, the above method cannot dynamically query the content of the engine during the implementation process, and it is not easy to locate the problem of the model during the execution process

Images