This is a design question and good practice question. How do you structure your Java web development such that a lot of logic is not in the JSP file. Should you use any of the JSP tags for if structures or loops. I see a lot of code where the logic is hard to follow because of poorly designed JSP files. And then when you want to output to a different format like a PDF or XML document, you can't do it because all the logic is in the JSP file.
Are there any tips or practices that you follow for Java Web development.
I am currently using a combination of Spring, Hibernate, Struts...and work with some Servlet code.
There are good practices associated with Java development. Many of us that have worked a while know them. What are some good practices for JSP development.
The easiest way to avoid placing logic in JSPs is simply to perform all that logic before forwarding a request to a JSP. The only logic you should need to do in a JSP is some basic looping (e.g. for creating HTML table rows), evaluating conditional statements, and data formatting.
All of this can be done without using scriptlet code (Java code) in the JSPs by using JSP tag libraries and EL. The most important tag library is JSTL. The JSTL tag library provides most of the logic you should ever need to perform in a view, though you may occasionally also use niche 3rd party tag libraries like displaytag which can reduce the amount of JSP code you need to write for specific tasks.
Since you're already using Spring you may want to check out Spring Webflow. I assume you're using Spring form tags, but if not, you should check those out as well. With this combination there should be very little need [if any] to use JSP tags in your view logic.
Related
Considering JSP should only be a view and shouldn't be making any calls to the database, then why do we have JSTL sql library? Isn't the availability of such tags tempt us in making database calls from JSP. I am sure it is there for some purpose but don't know what it is. I would like to get some opinions on it.
You're absolutely right. There shouldn't be a sql library. The first thing the official tutorial says about it is:
The JSTL SQL tags for accessing databases listed in Table 14-8 are designed for quick prototyping and simple applications. For production applications, database operations are normally encapsulated in JavaBeans components.
which is a diplomatic way of saying: don't use this. If you're using it, you're doing something wrong.
Every JSP needs to show the data and data source could be from say webservice, sql etc. So although it should be model who should fetch the data but still there are cases where you can't ignore sql call from JSP (say for e.g. if you are moving from legacy scriptlet to pure jstl) in that case you could use sql jstl library.
I'm really new to JSP and Servlets and all that jazz, and I'm confused about how to approach it.
Right now my main confusion is as follows:
It seems there are two ways to get a web page to display on the screen in a Java EE/JSP project:
Create an HTML page with the extension .jsp and in the web.xml file, map it to a url pattern (let's assume just /)
Create a Java class that extends Servlet, override the doGET() method to return a string of HTML code and map to this Java class in the web.xml.
My JSP project requires a decent amount of Java code to perform logic and login/logout operations. I've read that it's bad practice to inlcude Java code inside JSP pages as it becomes impossible to reuse, hard to keep track of, messy etc. I want to include much of code in Java, which will feel much more natural for me.
How should I build my project (assuming it's a simple beginner project in which I want to employ the best practices for organization, testing etc in preparation for building a larger project)? How can cleanly deploy web pages from inside Java classes, rather than having many JSP pages containing bits of Java code?
The pattern I've used in the past is to:
1) Write the servlet to perform whatever logic is necessary and to construct a reasonable number of serializable java objects to hold all of the data you want to be rendered via HTML.
2) The servlet stores those objects into the HTTP request and forwards the request and response objects to a JSP:
request.getRequestDispatcher("/some.jsp").forward(request, response);
3) The JSP can access the java objects in the request and merge the data with the static HTML to complete the request.
This is exactly the problem MVC pattern solves.
You do all your complex logic in the Controller (simple Java class, or a Servlet), then pass the data to View (JSP, Velocity, Freemarker, anything that can process the data and make a HTML).
There are several implementations of MVC for Java most popular being Spring MVC and Struts. Alternatively, you can just use your servlet for all your logic and then manually forward the request to a JSP for processing:
request.getRequestDispatcher("/index.jsp").forward(request,response);
If your are looking for best practices in clean separation of java code from the presentation, you might as well use a MVC Framework (Spring MVC or Struts are well know examples) that will help you to cleanly separate :
view layer (JSP)
controller layer
service layer
domain objects
persistence layer
It may be hard to begin with, but you will find nice tutorials through official sites and google.
If you want to only use servlets and JSP, the common rule is to have all logic and Java code in servlets, and that those servlets simply forward to JSP pages that will do the view part. The communication between then is done with request attributes (and of course, session and application context attributes.
Good luck ...
To manage bit of java code, you can use Scriptlet.
Also mentioned in other answers, you can use jsp:forward or response.sendRedirect
to call web pages.
Also see What is the difference between jsp:forward and response.sendRedirect
I'm not sure where you heard that its bad practice to include Java code in the HTML(JSP) files but in order to have a dynamically data driven website, Java is what you would use in the HTML(JSP). Keep in mind, all of your front end design will be in the HTML using JSP, and all of the your logic for handling requests and redirectors and passing data will be managed in the servlets using Java.
Your servlets can pass data, whether it be from a database or other data source, to the front end and your JSP will just help in displaying that data. It's called JSP for a reason. You can write Java in it.
The best approach for designing websites in Java is to use the MVC pattern that way it helps seperate all of the core functions of the site and can easily be scaled and managed.
Do you have any code that you have to show what you have done so far?
Are there any sample / tutorial on Spring MVC with JSP without using Tag Libraries. Pure JSP.
I am not conversant with Tag Libraries and I am good with JSP. So I would like to see if there are any examples and tutorials using pure JSP without ANY tag libraries.
I don't mean to say this in a degrading manner, but if you are good with JSP, you should be able to pick up the Spring MVC tags easily. JSP, custom tags and ELs go hand-in-hand. They are created for a reason: to make your life simpler. A quick example, if you use Spring MVC's form tag, Spring MVC will automatically prefill the form fields for you based on the data you have in the model. Think about how tedious your code will be to prefill the checkboxes/radiobuttons or preselect the drop down lists.
If you are also Spring Security, the provided custom tags allow you to easily control what data to be displayed based on the user roles.
Writing all of that using pure JSP don't even make sense to me... not to mention the amount of time wasted writing less than perfect home grown solutions.
I am a front end or UI developer with limited understanding of Java. I have a java based web app with JSTL used in it..I would like to understand the exact use of JSTL. Is it always used within JSP pages and is it used only for getting data from the database. Could you please explain with some basic examples..
JSP tags are used to generate HTML dynamically in a JSP, but without mixing Java code and HTML markup. The JSTL is a library of standard JSP tags. It means "JavaServer Pages Standard Tag Library", and as its name indicates, it's used within JSPs.
It should never be used to get data from the database. Getting data from the database should be done before executing the JSP, in a controller written in Java. Once the controller has done its job, it should dispatch the HTTP request to a view (the JSP), whose role is to render the data.
So if your application uses sql tags, then it's wrong. core and fmt tags are OK. As the Java EE tutorial indicates :
The JSTL SQL tags for accessing
databases listed in Table 7-7 are
designed for quick prototyping and
simple applications. For production
applications, database operations are
normally encapsulated in JavaBeans
components.
JSTL - JavaServer Pages Standard Tag Library - was designed to overcome a shortcoming in JSP, namely that a simpler way was needed to invoke Java libraries from the JSP page. The previous way to do it was to escape into Java with <%, %> and <%= and do what you needed, which led to very complex and difficult to maintain JSP pages.
JSTL give you new tags in addition to the HTML-tags you have in your JSP-pages, but which have special meaning server side, so it is interpreted when asked for by the client, and the result put in the actual page sent back to the client.
The tag definitions can do anything you can do in Java but you should strongly consider what you do where. Having e.g. SQL requests in your JSP-page mean that you tie business logic together with actual presentation, which has been - painfully - learned also gives complex and difficult to maintain web applications.
Is it always used within JSP pages
Yes.
... and is it used only for getting data from the database.
No. In fact, in most cases it is bad practice to access the database from a JSP, using JSTL or using other means (e.g. scriptlets).
does it mean like most JSP would have an associated Java file like 1-1 mapped, where the logic to get data using SQL query is written and is given to the JSP page.
Sort of. But there is not necessarily a 1 to 1 mapping:
Not all JSPs need to access the database.
A Java servlet may use multiple JSPs to render different output pages.
Different servlets may share a single JSP; e.g. to render a common error message page.
If yes, what exactly is the role of JSTL code within the JSP.
The aim of a JSP is to render output; typically HTML pages, but it could be anything text-based. JSTL is used within JSPs when the the output rendering logic is too complicated or messy to express using JSP EL.
UPDATE
The old-fashioned alternative to JSTL and JSP EL is to embed Java code ... i.e. scriptlets ... in the JSPs. For example:
<c:if test="${a == 'true'}">
hi
</c:if>
is equivalent to something like this:
<% if ("true".equals(context.findAttribute("a")) { %>
hi
<% } %>
Also for JSTL use, from what I understand, it is used within the JSP for dynamic HTML rendering through if-else statements.
You are describing HTML whose structure and content depends request parameters, configuration parameters, data fetched from the database and so in. This is the primary uses of JSTL.
However, this is NOT what is normally referred to as "Dynamic HTML". Dynamic HTML is where the browser changes the HTML of the currently displayed page, for e.g., when Javascript embedded in the page changes displayed page by modifying the DOM.
JSTL is a "custom tag library set" developed in and for the specifications of the J2EE server JSP servlet engine section. "Any tag in a Java J2EE spec. server markup page" configured for the java server written in Java2 J2EE spec is a "Custom Tag implementation" whether JSF , JSP , JSTL or Databasing cudtom tag. However it is not a Java Bean (only extremely similar to them in syntax and semantic to write a class program).
Each custom tag library has its own set of useful properties in java server markup and is why the system was developed. The Java Bean system is alike but is done through EL language.
A "tag" uses both a markup representation in the page and its co-bound(configured) .class file program in the server to process page markup and interface or join other server processes and programs.
JSTL is simply java server markup library for the JSP-servelt engine as JSF is a markup for the faces-servlet engine and both are only a custom tag.
If I let anyone modify a freemarker viewpage, can I somehow make it hack free?
I know I read somewhere that I can make disable scriplets, but that was for .jsp pages so not sure if it will work with freemarker.
I basically want a way where I can set the attributes that will be available on the page, and let web designers go into the page and edit it all they want (all the while making it secure).
i.e. I don't want people to be able to access any of objects in the request pipeline, or output my connection string to the page etc.
Request and other objects are exposed to the FreeMarker template by Spring's FreeMarkerView, when FreeMarker is used as a Spring MVC view technology.
To have a full control over the data being exposed to the templates, you can use FreeMarker directly, as described in the FreeMarker docs. However, you can still use Spring's support for FreeMarker configuration (FreeMarkerConfigurationFactoryBean).