This article explainsJ2EE ApplicationAnd describes how to develop a simple rule engine for a popular spring framework. This article requires readersSpringHave a basic understanding.
Any larger software project contains many things called business logic. The exact description of the business logic is still controversial. In a large amount of code generated for typical applications, fragmented code is everywhere for functions such as order processing, weapon control systems, and graphic rendering. This code is significantly different from other types of Code such as processing persistence, logs, transactions, language preferences, framework features, and other modern enterprise-level applications.
Business logic is usually closely integrated with other code blocks. When a heavyweight intrusive framework (suchEJB) When used, it is very difficult to distinguish the business logic from the code generated by the framework.
There is a software requirement that is difficult to accurately describe in the requirement definition document, but has the ability to make the software project succeed or fail: adaptability, which is used to measure the software's responsiveness to business changes.
Modern Enterprises require fast response and flexibility, and they have the same requirements for enterprise software. The business rules that you have worked hard to achieve today may be abandoned tomorrow and require you to change quickly and accurately based on the changes. When your code that contains the business logic is hidden in a large number of other code, modifications become slow, painful, and error-prone.
Read: http://www.javah.net/Spring/20070426/453.html