Introduction to JSP Technology

I saw this article on the Blog of an employee of Neusoft. I don't know if it was original, but it feels good after reading it. Think about returning to school this semester. I decided to complete the course in early March. The course was completely in the learning stage throughout March, April, and May, and basically did not write a few lines of code. The general learning process is: HTML, CSS, JavaScript, VBScript, Java language, AWT, Swing, Applet, Servlet, JSP entry, JDBC, MVC, Struts, and Hibernate.

Now let's look back at the learning process, which is roughly the same as what I wrote in this article. It seems that my learning method is basically correct. But it also took a lot of detours, such as the learning of Applet and AWT. Now it seems that it is useless. Currently, Swing is basically used for graphical interfaces using Java, the AWT event processing mechanism has been replaced by the listening mechanism. As for the Applet, it is rarely used. I feel that it is better to build a Flash than to write an Applet embedded into the page.

Now I think it is interesting to look at my own setup code, because sometimes I Write System Code while learning, and some technologies cannot be used in the system if I have not learned them, so the current system is not only in code, but also in the pattern design of the system. From the initial single-layer structure, all functions are implemented using JSP to the later two-layer structure.

Bean; then to the later use of the MVC three-layer architecture and Struts framework. Fortunately, the system functions are divided into modules. The relative independence between modules allows me to change the system architecture relatively freely. I am so lazy now that I don't want to rewrite the previous Code. Fortunately, there is very little single-layer code, and the teacher will not check it one line at a time. However, the system UML diagram should be modified in the paper, or the teacher will find it at a glance. Many functions added to JSP pages should be extracted and put into related Java classes.

I feel that the five-month learning time provided in this article is quite practical. Of course, this refers to the full-time study of these technologies. Now it takes less than three months to complete this plan. Many of the technologies are not very deep in learning, and the most important thing is that Servlet learning is not enough, in the JDBC section, the database connection pool is not configured in practice, XHTML is not involved, and XML learning is not deep enough.

In addition, I want to add two items to this full plan:

Learning and understanding of the MVC model and the use of the Struts framework. The teacher talked about MVC for countless times in class, but he had been confused about the mode layer and control layer. Now he has his own understanding: View-GUI, responsible for data display, regardless of the meaning and source of the data, the model is data and data processing, regardless of the reason for Data Reading and Writing. The controller is the business logic and is responsible for data processing, regardless of the specific read source and data writing process. Now I understand the three layers of Struts. If someone asks me how to differentiate the mode layer and control layer in Struts? I will confidently tell him that the mode layer and control layer are unclear to a certain extent. It depends on your understanding and happiness. Haha, It's a sophistry, but this is what the IBM consultant said, indeed.

The learning of Hibernate has now gone deep into all aspects of software engineering. Database Operations are no exception. Object-Oriented Databases have emerged. Although advanced technology, they have not yet entered the practical stage. Hibernate is an object-oriented database operating technology, and a new persistent layer has emerged in the system. The learning of Hibernate is still in its infancy. Due to the time relationship, it is a pity that related technologies cannot be used in the design. Now, we can only focus on writing papers.

I think it is more appropriate to change the title of an article into a full growth plan for Web programmers, because I feel that many people equate Web development with JSP technology, however, I think the JSP technology is just a graphical interface tool. Other data processing needs to be implemented in related Java classes, including Servlet.

To learn HTML for page design, we should look at the source code of some beautiful pages. In fact, we will find that many beautiful interfaces are implemented using Table labels. Through the nesting of tables, regular pages are stored in tables. Some dynamic effects, such as dynamic menus, usually place the dynamically displayed content into the DIV, add the required attributes for the dynamic change to the div through CSS, and then control the attribute changes at the layer through JavaScript or VBScript.

JSP technology is a cohesive technology that successfully connects to other technologies you need to understand. If you already know Java, HTML, and avascript, this means that JSP is indeed simple.

Find an HTML tutorial on the internet, familiarize yourself with the HTML syntax, and make a static web page; download JDK, TOMCAT, and so on, configure the JSP environment, and then find this JSP tutorial. You are also familiar with the syntax first, next, I tried to write a dynamic web page to connect the database and basic database operations. Then I went to the Java tutorial and learned more about the Java class.

First of all, let's get started with JSP. Let's take a look at Tsinghua's "JSP practical tutorial". Of course, if you don't even know the basic html, just add the html first, understand JSP syntax, and content such as request, session, and so on, and then learn Javabean and servlet. Java is required at this time, so we need to lay a solid foundation for Java. Let's take a look at the Java book, for example, in Java programming ideology, remember to keep coding practices constantly. The hacker can make it happen, and then read documents from the csdn community or document center, learn your experiences and skills.

I use dreamwaver to write JSP pages and jbuilder to write Java pages. However, these tools are designed to save time, but they do not need to be used.

This process is very difficult to learn. It is better to say that it is difficult to complete, because I don't have this patience. I am a little bit arrogant, but I can't do it without learning it, there is no way to be lazy, but system learning is only good for you:

1. learn HTML first, and then Javascript again. If you can learn CSS or something, it will be better to make sure that the web page you made is not ugly.

2. Configure the JSP environment, install JDK, TOMCAT, and JSP, and create a simple dynamic web page.

3. Learn SQL syntax first, and then Install SQL
SERVER, MYSQL, and ACCESS. Let's talk about it later in ORACLE.) Learn How to query, update, insert, and delete data in a simple way.

4. First, learn the basic Java syntax, and then find a ready-made example such as JavaBEAN and SERVLET. If you do not understand or cannot figure it out, let's ask here.

5. Finally, you can design a project on your own. Congratulations, you are already a master. How to become a successful JSP programmer? A common error is to treat JSP as a simplified Java. It is not. In fact, JSP is a simplified servlets .) Programmers usually try to learn JSP directly without learning the required support skills. JSP technology is a cohesive technology that successfully connects to other technologies you need to understand. If you already know Java, HTML, and Javascript, this means that JSP is indeed simple.

JSP programmers need to become a successful JSP programmer. Refer to this timetable. Note the following:
◆ Ignore the steps you are already familiar.
◆ The training time only indicates that you have learned enough basic time to move to the next step.

These trainings are the core of JSP. You don't have to learn all of the above, depending on what tasks you assign to your project and what knowledge you have. But this is my schedule for successfully training programmers. The key unit is time. On average, five months can indeed train a person (from the beginning to the completion) to become a programmer familiar with JSP. Five months seem to be a long time, but it is far more than what a senior WEB programmer has learned.

Maybe you think it takes too long to get started with JSP, because learning ASP is faster and the time is shorter. However, learning ASP does not require learning Java.

1. Adding special characters causes exposure of JSP source code files
2. Use JMeter to test JSP Application Performance
3. Multi-thread synchronization in Servlet and JSP
4. Analysis of the best solution example of JSP IIS
5. Can JSP meet the Web boom?