Ferdinand Victorinus wrote:I've already seen large code blocks inside JSP's, in a way it is very hard to maintain the web application.
Yes, it's hard to read, hard to maintain, impossible to test, and can't be abstracted or reused. It's a terrible way to write code and yet it continues to this day.
Read this article to start learning the proper way to structure a web application.
Ferdinand Victorinus wrote:I've already seen large code blocks inside JSP's, in a way it is very hard to maintain the web application. Is there a way to avoid that?
Not only is it very hard to manage, but also a very poor and outdated practice, outdated about 8 years ago. The best way to avoid it is by following a MVC (Model View Controller) architecture to begin with.
the following are the advantages of using the MVC arch.
Learn to use get and setParameters or get and setAttributes. Also learn to use EJB (enterprise java beans). Also implement JSTL Tags. This a cleaner method of writing jsp pages.
hope this helps.
Sooraj Rajagopalan wrote:the following are the advantages of using the MVC arch.
advantages the logic stays hidden from the user processing and logic solving will be done at the server side keeping the client side complications to the minimum will reduce the incompatibility issues to the minimum.
None of these have anything to do with MVC, and none are relevant in the scriptlets-pros-and-cons debate; what point are you trying to make?