J2EE development learning Summary

I haven't posted a blog on csdn for a long time. I just logged on to my post and read a learning summary from my freshman summer vacation. -_-

Now that I have graduated and have less than a year of work, I will re-publish a summary. Of course, it is still about J2EE development. Because I have always been working in this direction. In my opinion, if you do not know how to pass by, please point out.

Go straight to the topic without talking nonsense.

J2EE, the basics are still Java, and we can understand what object orientation is. Class, object, heap, stack, set, multi-thread, Servlet, it is best to thoroughly understand these things. If you don't understand them, remember the definition first, first use it, and gradually understand it later.

Data structure. Be familiar with at least three algorithms. Classic is Bubble sorting, binary search algorithm, and direct sorting algorithm-just for example, do not stick to it. A good habit is to try to write a small program to solve some repetitive problems in your life.

Software Engineering is required. I personally think it is necessary to understand, be familiar with, or even be proficient in the general process of software development. If you are not a programmer, you are advised to write documents. Requirement documents, outline design documents, and detailed design documents. These things have no special stereotypes and there are many resources on the Internet. I will not repeat them here.

Software testing. Although we do not do the tester many times, we still need to understand its importance. In this way, we can develop good programming habits in future programming.

Database: if you are not determined to be a database administrator, you can understand General SQL statements, common query methods, and statements. Stored Procedures, functions, triggers, and other things. You can also practice writing and writing, and then use your own program to call and call them. You will encounter many problems and crash many times. When you crash, ask du Niang (Baidu), where the wealth left by thousands of Nb predecessors in the online world is. Select a database and get familiar with it. The so-called familiarity means that when you encounter a common scenario, you can solve it without asking du Niang. Currently, the mainstream Database SQL Service, MySQL
, Oracle. I have to say that some companies are still using access, with a good foundation, and it is too late to learn it.

PS: it is also very important, programming habits. I suggest you go to the Internet to find a set of highly regulated programming protocols to form your own good programming habits and make your code as readable as possible.

Advanced learning is MVC. That is, model, view, and control. You can say that this is a framework, a development mode, or even a standard, see what you understand. I personally prefer to understand that this is a standard, a hierarchical model development standard developed based on the object-oriented thinking.

At this stage, it is best to develop some small issues on your own and use MVC to do so. It is best to do so. If a complete system is seated, it will inevitably benefit a lot. Of course, the various errors encountered in this process will also cause you to crash for countless times. Every time a crash occurs, remember one sentence. If you have any questions, ask du Niang.

Finally, the question is final. Ssh, namely struts2, spring, and hibernate, are the three frameworks that are standard for J2EE development. These three frameworks can be used in combination at will and can be used independently based on their respective capabilities and preferences.

The recommended learning and use sequence is struts, then hibernate, then STRUTS + hibernate, and finally integrate ssh.

The framework is simple and complex. It is easy to use. It is difficult to master the principles, but not impossible. Individuals are still exploring. Currently, we are proficient in integrating SSH into the system. You can quickly troubleshoot exceptions.

It doesn't matter if you don't understand it. Use it first. It's okay to know how to use it. Then, I often go to the documents, help documents or APIs, both in Chinese and English, and then combine the problems I encountered in the use process to ponder over and guess the principle, and then test and test, confirm.

Don't rush for success. When struts is ready for use, it is anxious to get hibernate. Hibernate is eager to integrate it as soon as it finds a point. This endless stream of problems is enough to let you crash.

I personally suggest using struts2 to create a small project, rebuild the project with struts2 + hibernate, and then rebuild the project with SSH. Or three different small projects. As for why I always say it is a small project, rather than an enterprise-level project, you will know when you do it.

No matter what you do, your attitude determines whether you can do well or how far you can go on this road. Sharing with you ^_^

Personal original works, reproduced please indicate the source: http://blog.csdn.net/yang_lover/article/details/8268756