Why JSP cannot replace servlet

Js|servlet Why JSP cannot replace servlet

Blueski compilation

JSP Dynamic Web content may be a great technology for dynamic Web content and can separate content from presentation presentation, and some people still find it strange why servlets still need to be implemented at the same time as JSP.

In fact, the practicality of servlets is not a problem. They perform very well on server-side processing and continue to exist because of their compelling installation practices. In fact, you can view the JSP as a servlets high-level abstraction, which is implemented in the form of a servlet 2.1 API extension.

You should still not use servlets selectively; they may not apply to everyone. For example, when a page designer can easily use a handy HTML or XML tool to write JSP pages, Servlets may be better suited to those on the back end, because they often use some kind of IDE to write-a process that typically requires a higher level of programming experience.

When publishing servlets, even developers should not accidentally ensure that there is no close integration between presentation and content. You can usually do this by adding a third party release package such as Htmlkona. But even if you can do this, although you can provide some flexibility through simple on-screen adjustments, there is still no way to guarantee changes in presentation's own format. For example, if your presentation changes from HTML to DHTML, you will still need to make sure that the release package is consistent with the new format, and that in the worst-case scenario-scenario, if a distribution package is not available, You will end up using handwritten code for presentation in the content of the Dynamic Web.