Service rule automatic-calling method based on XML

[0064] A specific embodiment of the present invention is as follows:

[0065] An XML-based method for automatically invoking business rules, including:

[0066] S1. Process the user request URL to generate a user interaction interface;

[0067] S2. Obtain input data of the user interaction interface and business operation instructions on the user interaction interface to generate instantiated entity XML, including:

[0068] S21. Obtain the corresponding form configuration according to the URL requested by the user, and after parsing the form configuration, call the corresponding interface HTML control to generate a user interaction interface;

[0069] S22. Acquire business operation instructions on the user interaction interface, and initialize entity XML in combination with the acquired entity XML structure; business operation instructions include save, delete, modify, and add, etc., and are based on the user's interface HTML controls on the user interaction interface Obtained by the operation;

[0070] S23. Read each HTML control on the user interaction interface in a loop, obtain the datafield attribute of the HTML control, and determine whether the path of the datafield attribute has a corresponding node in the entity XML, if it exists, then obtain the node, otherwise in the entity Insert a corresponding node in XML;

[0071] S24. Determine whether the HTML control is a container control, if not, obtain the value of the HTML control's value range, and assign the value to the corresponding node, otherwise directly execute step S25;

[0072] S25: Judge whether all HTML controls have been traversed, if yes, return the entity XML, otherwise continue to perform step S23.

[0073] S3. Parse the instantiated entity XML to obtain the corresponding business operation instructions, and then invoke the business rules bound to it, including:

[0074] S31. Parse the instantiated entity XML, obtain the corresponding business operation instruction, and determine whether the business operation instruction has a bound business rule, if so, obtain the corresponding business rule and continue to execute step S32, otherwise it ends;

[0075] S32. Read the first node of the business rule and determine whether the node is an operation node or an engine node. If the node is an operation node, continue to step S33, otherwise execute the corresponding engine operation and execute step S34; here, the operation node Corresponds to arithmetic processing operations such as save, delete, modify, and add. Engine nodes correspond to logical operations such as loops and judgments. Executing corresponding engine operations means performing corresponding operations according to the type of engine node, such as executing if statements, for statements, etc. ;

[0076] S33. Load the corresponding adapter according to the meta-component name in the node attribute of the node, and convert the entity XML into meta-component parameters through XSLT, and then call the corresponding meta-component through the adapter and the meta-component parameters. The node attributes include the name of the meta-component and the transformation relationship between the entity XML and the meta-component parameter. XSLT in this step refers to the transformation relationship between the entity XML and the meta-component parameter.

[0077] S34. Judge whether the node is the last node of the business rule, if not, return to step S32, otherwise end.

[0078] S4. The instantiated entity XML is formed into SQL data and stored in the database. Here, the instantiated entity XML is formed into SQL data and stored in the database. Therefore, in the subsequent processing, the queried two-dimensional table data can be instantiated into entity XML according to the acquired instructions.

[0079] It should be noted that when some meta-components are called, some meta-components (that is, the adapter mentioned in the present invention) that can call such meta-components need to be developed due to the operating system or its support environment. Therefore, this implementation The example uses an XML-based database access meta-component adapter.

[0080] The focus of this method is to call business rules through entity XML. In this embodiment, the acquired business operation instructions of the user interaction interface are also used to generate entity XML, and the entity XML is subsequently parsed to obtain business operation instructions, and then perform business operations. The call of the rules. In actual processing, it is also possible to directly index the business operation instructions and associate with the entity XML, and subsequently obtain the corresponding index data by parsing the entity XML, and then perform implementation methods such as invoking business rules. Any equivalent replacement of this method is within the protection scope of the present invention.