How does JSP and Servlet work together?

Servlet plays a controller role in MVC approach. JSP is the view in MVC approach for showing output. Servlet is faster than JSP. JSP is slower than Servlet because the first step in JSP lifecycle is the translation of JSP to java code and then compile.

As depicted in the above diagram, JSP page is translated into Servlet by the help of JSP translator. The JSP translator is a part of the web server which is responsible for translating the JSP page into Servlet. After that, Servlet page is compiled by the compiler and gets converted into the class file.

When a request is mapped to a JSP page, the web container first checks whether the JSP page’s servlet is older than the JSP page. If the servlet is older, the web container translates the JSP page into a servlet class and compiles the class.

You start with a JSP or a Servlet class. The server is responsible for instantiating the JSP/Servlet and it uses the new() method to accomplish this. This new() method is the Java method for creating space in memory for an object. After the JSP/Servlet is instantiated, the init(…)

When the JSPC(compiler) converts the code into Servlet code and calls the JAVAC compiler to generate the . class file.

JavaServer Pages (JSP) is a Java standard technology that enables you to write dynamic, data-driven pages for your Java web applications. JSP is built on top of the Java Servlet specification. The two technologies typically work together, especially in older Java web applications.

Jakarta Server Pages (JSP; formerly JavaServer Pages) is a collection of technologies that helps software developers create dynamically generated web pages based on HTML, XML, SOAP, or other document types. Released in 1999 by Sun Microsystems, JSP is similar to PHP and ASP, but uses the Java programming language.