JAVA Web Development model

JSP page run stage is divided into: translation, compilation, class loading, class instantiation, initialization, service, destroy seven stages

JSP Web page mainly consists of two parts of element and template data

JSP elements include: script elements, directives, standard actions

The Web container supports two different forms of JSP syntax in both plain and XML compatible formats

There are scriptlet, script expressions, and declarations in the JSP

The role of JSP instruction is mainly the communication between the page and the container

JSP actions are used to communicate between pages and pages or between pages and components (JavaBean)

There are implicit objects in the JSP that are used in manipulating requests, responses, sessions, and other Servlets

How to reference JavaBean in a JSP page

Understanding JavaBean JSP Correctly

Development Mode 1 JSP

Development mode 2 using filters as a controller in MVC

Servlets make Web application development cumbersome and not conducive to division and collaboration

Using JSPs (expressions, declarations, scriplet) to develop Web applications

Java Web Development Made Easy

The page is critically short of readability

No separation of page representation and business logic, increased maintenance difficulty

JavaBean is essentially a common Java class. The JavaBean component, which needs to follow a certain coding standard, has the following characteristics JavaBean class must be a public class and its Access property set to publicly. The JavaBean class must have an empty constructor a JavaBean class should not have public instance variables, and class variables are private.

To access these class variables, you should access them through a set of access methods (GETXXX and Setxxx), and you cannot begin naming member variables in uppercase letters JavaBean should be serializable (serializable), implementing java.io.Serializable interfaces

JAVA Web Development model