Original question: Why should I use JSP when there is already servlet technology available for serving dynamic content?
While JSP may be great for serving up dynamic Web content and separating content from presentation, some may still wonder why servlets should be cast aside for JSP. The utility of servlets is not in question. They are excellent for server-side processing, and, with their significant installed base, are here to stay. In fact, architecturally speaking, you can view JSP as a high-level abstraction of servlets that is implemented as an extension of the Servlet 2.1 API. Still, you shouldn’t use servlets indiscriminately; they may not be appropriate for everyone. For instance, while page designers can easily write a JSP page using conventional HTML or XML tools, servlets are more suited for back-end developers because they are often written using an IDE — a process that generally requires a higher level of programming expertise. When deploying servlets, even developers have to be careful and ensure that there is no tight coupling between presentation and content. You can usually do this by
Related Questions
- IP telephony is a dynamic area with frequent changes in technology; if we go to it now, what assurances are there that our investments wont be lost or stranded in a couple of years?
- Original question: Why should I use JSP when there is already servlet technology available for serving dynamic content?]
- Original question: Why should I use JSP when there is already servlet technology available for serving dynamic content?
