Using a simple Web development architecture

Using hibernate to persist data, use a servlet to do process control and communicate with business logic classes, update databases and fetch data, and produce XML to include all of the data, and then use XSLT to process XML and output HTML, so the structure is relatively simple, Completely separated from the MVC three layer, and from the current few projects, the effect is good, and the development speed is good, but the key problem is to have a good XSLT people. It should be in the case of good detailed design or prototype, the developer to write the XML files required by the page, and then the interface personnel based on XML and prototypes to do XSLT, at this time, developers and interface personnel can be clear division of labor, and will not appear, and so on. In addition, this structure is relatively easy to test for the performance of the interface, but it is only the generation of XML, business logic, and data persistence test, such testing is relatively easy.

Compared to the current market mainstream web framework (struts,webwork, etc., there is no derogatory meaning of these frameworks) is simpler, in fact, no matter what framework as long as the appropriate for your current development is a good framework (even if not a framework), now feel that the Java people seem to be a bit of an obsession, When I do something, I think of the framework, the structure, it is not necessary, now the framework of new so fast, we can keep up. Don't everyone feel tired of being a Chinese programmer (but I like it). Generation, business logic, and data persistence tests, such tests are relatively easy.