Some Ideas about SSH

1. struts1 is simple, reliable, boring, and cool. It supports various tools to meet the needs of applications such as most forms-> query-> databases. It should be said that it is not uncommon to use struts for websites.

2. Spring and IOC are a good concept. The problem is that XML is too annoying. How many opportunities will it be changed in the future? To be honest,My pairCodeReuse with reserved opinions-- Either use a mature framework or tool, such as log4j, or start from scratch. In addition, spring makes the read code more complex. In fact, the read code itself is very complicated. However, with the help of tools, you can easily jump from one class to another, using spring, all dependencies are stored in XML, and it is difficult for tools to help.

As for the spring MVC framework, I think it is similar to stuts.

3. hibernate. Well, after writing crud code for so many years, you should change your taste. Good tool support: UML-database table-reverse engineering to hibernate class (pojo abstract class + Implementation class) and various configuration files. With the support of tools, database table design is actually the simplest thing (think about what it feels like if you write 100 pojo classes, and if the design is changed, you can write it from the beginning ......), The tool not only reduces the workload, but also ensures consistency from design to code.

But why not select the query language?

Sorry, netbeans has poor support for hibernate ...... Use myeclipse.

4. JPA and hibernate official version. Thanks to God, at least you don't need to write XML. The annotation-based method makes code and maintenance much easier. Of course, for understandingProgramFrameworks are of little use-I prefer to understand their relationships from class diagrams rather than reading comments in classes. Of course, it is a perfect tool, so it is still a reverse engineering of UML-> database table->.

I like the query language like SQL .......

BTW: JPA can also be configured using XML, or can be separated from containers (such as WebLogic? Tomcat ?) It is used separately.

I personally think that sh or SP is good enough (struts ).

Welcome to shoot bricks (this, preferably technical bricks .....)

Development process? Use Case-analysis class-activity diagram, sequence diagram-implementation class-deployment Diagram
Tools? Myeclipse (or eclipse EE, and then find the plug-in by yourself) + Power Designer (really easy to use .....)
Database: Oracle? SQL Server? MySQL? Java db? (It is best not to use it. The performance is poor, and there is a paging problem. Only the latest version supports part of the paging function. Of course, it stores 1 ~ Small records are acceptable)
Configuration Management: CVs? In fact, VSS is also good, P4, but if you do daily testing and creation, you must use a tool that supports ant.
Defect management: Bugzilla?