The overview of HTML forms is given. This includes the creation, use the communication models and as well as the service side interaction which is done by the request-response model in the web is introduced.

The form by JSP is shown here. Here the basic template is made which contains the radio button, drop down menu and the basic input field. Here this can be acquired by the JSP file by the request get Parameter field. Hence this can be displayed in the browser.

This is the same type of tutorial, the only difference being that here Servlets are used instead of JSP. This changes the functions and the important point is that the form action type determines which of the method (Do Get or Do Post handles the data in the Servlets).

The basic validation done to the HTML form is shown here. It is done by the HTML attributes such as required and checked. Hence this prevents the basic mistakes that take place in the submission of a form.

At the end of each section, we provide you with the source code of all the programs implemented in the section. The tutorial for extracting and using the files have been discussed earlier in the previous section.

This tutorial deals with beans in Java. The beans in Java is a class which contains attributes which can be used by other JSP files in the project. Here we use two JSP files to set and get property of the attributes in the bean.

In Beans, while assigning any attribute there is a scope that is a rule which is applied for variables such that they can be viewed in certain pages and certain browsers. Here the various scopes and declarations are described. Here the session, application and page scopes are seen.

As compared to the above scopes, a new scope is seen which is the request scope. Here a separate copy of response and request is maintained for each page, which can be navigated to another page.

As we have seen the forms which are submitted to a servlet and also JSP files, here the same forms are submitted and acted upon with Beans.

At the end of each section, we provide you with the source code of all the programs implemented in the section. The tutorial for extracting and using the files have been discussed earlier in the previous section.

Here the summary of a session is given in JSP. In JSP, the session variable tracks on the user as the user visits the particular website and performs activities on it. Here the track is maintained on the basis of a request-response model.

In JSP cookie is a text file which is stored in the users’ computers when the user interacts with some website. JSP support the HTTPs cookies. It keeps track of the user's activity. For example, the cookie saves the login and password of the specific website so that we don’t have to enter it each time we have to login into the website.

As explained above the cookie saves the user info each time it accesses a particular website. Hence the read of the attributes as we enter and writing functions of the same is shown. Here given is the working of such cookie.

As the cookie performs the read and writes operation of a user login in a web page, in the same way, the user can be redirected to the home page of a website via cookie after logout. Hence this as the above includes factors such as the time exceeds and etc. which have to be used.

Hence as stated above the user can be logged out even using the session attribute where the inactivity of the user for a certain amount can result in the logging out of the user from the user. The User in such scenarios will have to log in again.

This tutorial shows that how the web pages (specifically the homepage) can be organized whenever the project is executed. Then the application is redirected from the home page to the specific tab as per user convenience.

This tutorial deals with the organization of the application where the various links such as the login redirection or forwarding and similarly logout redirection are dealt with the servlets. Here the total project is configured such that the log out immediately redirects to its homepage and on the login, the home page directs it to a specific page.

There might be cases where cookies and enabled in some sites. But if the cookies are disabled within some sites, then, in that case, we can use the encoding of that URL such that the session ID is stored in the URL. In such ways, tabs can be kept on a particular session.

The servlets filters are introduced in the lecture. The servlets filters are used when multiple pieces of code are used repeatedly in multiple pages for various purposes like authentication or user access for a particular page. Hence this topic is explained with the example in the lecture.

At the end of each section, we provide you with the source code of all the programs implemented in the section. The tutorial for extracting and using the files have been discussed earlier in the previous section.

This tutorial deals with the JSTL which stands for Java Server Page Standard Library. The JSTL library has tags which are categorized into 5 main categories which are described here and also the uses of the tags are to make in a project which will be described as we go along in the tutorial.

This deals with the tags (core) set and remove. This can be imported by the taglib command which is shown here and which can be done in various ways. The taglib command is just like the import command in the java. The use of set and remove tags is shown in Java.

This tutorial deals with a reading of bean attributes with the help of JSTL library. The bean is an entity class available to us which have some properties which we can use further down the line in the project. Hence reading and printing of the attributes is seen here.    

This tutorial deals with the decision making in JSTL. Here the same example is given by the if condition. Here we can note that there is no else condition and hence only if can be used to make decisions.

This tutorial deals with the above tags. These tags are ‘choose’, ‘when’ and ‘otherwise’ tags. The tutorial shows the use of these tags along with their implementation and conditions or situations for the suitable use of such tags.

This tutorial deals with the for loop in JSTL. Hence it's used is shown where the attributes such as begin and end are encapsulated in the tags and the output is shown with the help of expression language.

This tutorial deals with the for each loop in JSTL. Just as the above tutorial its use is shown where the attributes such as begin and end are encapsulated in the tags and the output is shown with the help of expression language.

This tutorial deals with them for tokens which are used in the JSTL language.  The item attribute which is used in the tag is separated by the character given in the delimiter attribute.

Hence the URL can also be separated into its subsequent parts which can be used further.

The import and read parameter tags are explained here. As explained earlier the import tags are very useful chunks of code and which can be used to reduce the redundancy of code throughout the project files. Here as an example the header and footer are stored in a file and hence this can be imported in the required files.

The above tags are explained in the JSTL. The URL tag is seen before which is shown by the ‘href’ tag in HTML which is done here by the taglib in JSTL enclosed by the same ‘href’ tag. By using the redirect tag, the browser automatically redirects the user to the specified address.

The tutorial deals with the catch tag. The catch tag in JSTL is used to execute the remainder of the page in case of any exception occurs between the catch tags, the browser ignores it. We can also display the error with the help of expression language.

At the end of each section, we provide you with the source code of all the programs implemented in the section. The tutorial for extracting and using the files have been discussed earlier in the previous section.

Here in this tutorial Servlet Context is explained. Servlet Context is an Object used when the web application is started. It contains various initialization parameters which can be accessed through and controlled by the web.xml file.