Design And Implementation Of The Data Persistence Component Based On J2EE

In order to realize data-sharing, data should not only be accessed (that is to be connected with UI and to be managed following a series of principles) but also be perdured. As a result, with regard to the systems connected with data, the design of Data Persistence becomes quite important; what is more, with the development of data formatting of information, more and more management systems appeared. If the systems are to be designed with a goods tructure, the design of Data Persistenceis an absolutely necessity. For the sake of system transplant and maintainability, concision in design of Data Persistence is one of the key factors which should be considered. Therefore, extracting parts with little relations with business logics as a component and using it in Data Persistence design of different systems can make the design of Data Persistence much easier. With the assistance of the component, common errors made by users will be reduced in some extent. In addition, whether framework of the component is a lightweight one or not is also one of the factors with key in fluences for popularity. So, research into the lightweight and reusable component for Data Persistence is worthwhile and useful.In this paper, firstly, how the logical layers are separated in J2EE development introduced. The principle, structure, mechanism, application of design patterns and etc of a component designed and implemented by author are introduced with emphasis. At the same time, support for ORM (Object Relational Mapping) is also presented so as to satisfy diferent programming habits of diferent users. During the introduction, the advantage of lightweight and reusability a represented especially. In order to prove the usability, concision and reusability of the component, it is applied with POJO and DAO to design the Data Persistence in project "Auditing System For INDUSTRIAL BANK". Finally, capabilities of query, insert, deletion, update of data between the popular ORM tool—Hibernate and the component are compared. High performances of data visiting efficiency are showed in the condition of isolated models. Advantages and disadvantages of the component are explained as a conclusion.