Make data persistence with Hibernate, use servlet to do process control and business logic, update the database and get data, and generate XML to include all data, then use XSLT to handle XML processing, output HTML, so that it is also relatively simple. The three layers of MVC are completely separated, and the effect is still good from the current few projects, and the development speed is also good, but the key issue is to have a good XSLT person. The developer should write the XML file required for the page, and then the interface personnel will be XSLT according to the XML and prototypes, and the developers and interface people can be divided into cooperation and will not Phenomenon of appearing. Alternatively, this structure is more easily tested for processing interface performance. In fact, it is only tested for the generation, business logic, and data persistence of XML, which is still easier.
Compared to the current mainstream web framework (Struts, Webwork, etc.) is relatively simple, in fact, no matter what framework is suitable for your current development is a good frame (even without any frame), now feel Java people seem to have a little walk into the magic. I think that this framework is, the architecture, there is no need, now the framework is so fast, can we keep up? Don't you feel that Chinese programmers are very tort (but I like). Produce, business logic, and data persistence tests, such tests are still relatively easy.
