How does jsp and servlet work

A part of the web server called the servlet engine loads the Servlet class and executes it. During execution, the servlet produces an output in HTML format. The output is furthur passed on to the web server by the servlet engine inside an HTTP response.

This makes the process more efficient than with the other scripting languages such as PHP and therefore faster. Toggle navigation Manh Phan. Please use ide. Load Comments. What's New. Most popular in Java.

More related articles in Java. We use cookies to ensure you have the best browsing experience on our website. JSTL is the standard tag library, containing a collection of taglibs that ship with every servlet and JSP implementation, including Tomcat. The "functions" library is just one of the taglibs included with JSTL. Another common taglib is the core library, which you import by calling:. This simple function is used to protect web pages from such attacks.

Now that you've got a handle on JSP basics, let's make a change to the example application. To start, locate the Implicit Object app in your Tomcat installation. The path is: apache-tomcat Here are the latest Insider stories.

More Insider Sign Out. Sign In Register. Sign Out Sign In Register. Latest Insider. Check out the latest Insider stories here. More from the IDG Network. Servlets run faster than JSP, on the other hand JSP runs slower than servlet as it takes time to compile the program and convert into servlets.

In Servlet, you have to implement both business logic and presentation logic in the single file. It saves time to respond to the first request which increases response time. It uses standard API that is supported by numerous web servers.

Programming languages like platform independence and ease of development. You can access the large set of APIs that are available for the Java platform. The web container makes threads for handling more than one request to the servlet. Easy coordination between two or more servlet to make web applications. Servlet containers support many other features like sessions, resource management, persistence, security, etc.

It does matter numbers of requests. When there is a request, there is a thread, not a process. Servlet is persistent until it destroys. Designing in a servlet is difficult and slows down the application.