I saw a forum original code name, although it is very simple, but the structure is very clear, Struts Hibernate, data operations use DAO mode, support MySQL and Hibernate (itself HB support multiple databases, estimates authoring In order to practice your own pattern foundation), it is also very simple to add other database support. Then it is worth mentioning that the DAO implementation class implements the Interface of a data operation, because the most data operation is INSERT, UPDATE, SELECTBYPK, so that each of our classes is good (provided for data Simple operation, it is not so clarified by multi-table operation structure, and it is necessary to improve).
Then track the HB operation and the process of BO-> VO, one word: good. It is the architecture I want to implement in the fps, HB generates BO to give this beanutil class processing, and assigns the property to the VO, VO to the TAG processing display logic of the front desk. One problem in this is: Bo-> Vo, I will handle the value of the BO to Vo, which will perform such logic.
Hey .... Happy life is nothing but this !!
