A financial website project is implemented with Struts Hibernate. The project is mainly my design, but the demand is not good, and it is dares to practice. I feel that I don't dare to face it later. Yes. I feel that the reasons are:
1. The impact of the design of the demand. If the design is not integrated, the latter weird demand changes will make the code icon in a dress, and the last clothes are of course not what you want. Conclusion: Designers need to have control over 80%, more than this range, sorry, second phase.
2. The execution ability is not strong. Mainly the task and power is asymmetrical, so that the group members have no absolute authority. For example, let the user objects, the group members insist on using Username, Password one, one place, last session All.
3. Generation of persistence depends on Synchronized Hibernate, which requires an abstraction of our own persistence on the basis, so that the next layer can be generated with any plug-in generated by Hibernate, and can even use JDBC.
4. The business logic is placed in the action in Struts, which leads to a lot of Action. You can add a business logic layer so that you can reuse the code or convenient to test.
