Where should we use JSP technology?

Where should we use JSP technology?

Where should we use servlet technology? Where should we use JSP technology? Why do we need a servlet when JSP technology exists? What is the difference between servlets and JSP?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSOA.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSOA.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Servlets are components which run inside of a container and handle server requests (typically HTTP) in a request/response manner. JSPs are template pages that can be comprised of Java code and markup (HTML) code. A JSP is ultimately interpreted, converted to a servlet, compiled, and executed. With this in mind, you can technically get by using just JSPs; however, this practice is strongly discouraged, since it can lead to a very tightly-coupled and convoluted mess.

Best practices suggest using servlets as front controllers for incoming HTTP requests and JSPs as formatting templates for dynamic markup of HTTP responses. This leads to a much cleaner design following instep with the model-view-controller pattern.

This was first published in March 2005

Back to top