Editing Jakarta Server Pages (section)

== Criticism ==

According to Joel Murach and Michael Urban, authors of the book "Murach's Java Servlets and JSP", embedding Java code in JSP is generally bad practice.{{sfn | Murach | Urban | 2014 | loc=§1 Get started right - The JSP for the second page | pp=46-47}} A better approach would be to migrate the back-end logic embedded in the JSP to the Java code in the {{code|Servlet}}.{{sfn | Murach | Urban | 2014 | loc=§1 Get started right - The JSP for the second page | pp=46-47}} In this scenario, the {{code|Servlet}} is responsible for processing, and the JSP is responsible for displaying the HTML,{{sfn | Murach | Urban | 2014 | loc=§1 Get started right - The JSP for the second page | pp=46-47}} maintaining a clear [[separation of concerns]].

In 2000, Jason Hunter, author of "Java Servlet Programming" described a number of "problems" with JavaServer Pages.<ref name="problems">[http://servlets.com/soapbox/problems-jsp.html The Problems with JSP] (January 25, 2000)</ref> Nevertheless, he wrote that while JSP may not be the "best solution for the Java Platform" it was the "Java solution that is most like the non-Java solution," by which he meant Microsoft's [[Active Server Pages]]. Later, he added a note to his site saying that JSP had improved since 2000, but also cited its competitors, [[Apache Velocity]] and Tea (template language).<ref name="problems" /> Today, several alternatives and a number of JSP-oriented pages in larger web apps are considered to be technical debt.