The core of the application system should be the business logic layer.
It can also be classified in itself:
1. Life cycle control and container. This part may control the life cycle of the component of the business layer. It is also possible to control the life cycle of other modules, or the control of the module-level life control container in other modules. (In the application server, the lifecycle control section in the EJB standard .P.s. At least two types of application level and session level)
2, business logic. Complete the main logical unit required for business needs. (Session bean in EJB)
3, business process logic. Determine the process relationship between business logical units based on the process of business. (Workflow)
The business layer itself is differentiated into other modules when the system is not large. For example: Struts's Controller can undertake the ability of "business process logic".
In a small Web system, you can also use the web built-in lifecycle range container such as Application Session to assume life cycle control.
In a relatively large system, such as using the application server, the system may handle the lifecycle management to the server.
Now the system is in China. Generally, it is not reached with the level of the application server, and most of them use only the web server. Therefore, more common systems act as "life control and containers" using the scope objects such as AppLiction session.
Therefore, the general system framework can abstract "business logic" and can accept the data of the session, which is a bigger increase in development efficiency. However, if the relatively perfect, use EJB and application servers, or at least write a session level life control container (application level can be managed).
