Disadvantages of Jsp's over Servlets
2 posts in topic
Flat View  Flat View

Posted By:   RV_RamaKrishna
Posted On:   Saturday, April 16, 2005 10:39 PM

What are the Disadvantages of Jsp's over Servlets?

Re: Disadvantages of Jsp's over Servlets

Posted By:   Murugesan_surandai  
Posted On:   Monday, April 25, 2005 05:56 AM

JSP consumes extra hard drive space and extra memory space.
For every 30K JSP file on the server there must be a
corresponding larger-than-30K class file created. This
essentially doubles the hard drive requirements to store JSP
pages. Considering how easily a JSP file can <%@
include> a large data file for display, this becomes a
real concern. Also, each JSP's class file data must be
loaded into the server's memory, meaning the server may
eventually store the entire JSP document tree in memory. A
few JVMs have the ability to remove class file data from
memory; however, the programmer generally has no control
over the rules for reclaiming and for large sites the
reclaiming probably won't be aggressive enough.

JSP requires a compiler be shipped with the webserver.
That's problematic, especially since Sun doesn't give away
the tools.jar library containing their javac compiler. Web
servers can package an outside vendor's compiler such as
IBM's jikes; however such compilers generally don't work on
all platforms and (being written in C++) aren't much help to
a pure-Java web server.

Re: Disadvantages of Jsp's over Servlets

Posted By:   alan_do  
Posted On:   Monday, April 18, 2005 06:24 AM

if you want a clean implementation of your codes, you need both, especially re: separation of concerns. if you plan to put your controller logic inside the JSP's, the disavantages includes (and definitely NOT limited to) mixing controller logics with views, LOTS of codes, exposure of JSP's (unsecured resources), oh, and no one will hire you in the future. -/a
About | Sitemap | Contact