To build web applications in Java, you need to understand the libraries and concepts that underly the higher level frameworks, and this course helps you to do that. The course covers writing a web application in Java using Servlets, JavaServer Pages, and tag libraries.
Many Java web frameworks, such as Struts, are built on top of the Servlet and JavaServer Page specifications and base libraries. To fully understand how these frameworks operate, and to be able to take full advantage of the facilities they offer, you should understand the foundations such frameworks are built on. This course takes you through building a web application using the base Servlet and JavaServer Page libraries. The course discusses the Model-View-Controller pattern using Servlets as the Controller and JavaServer Pages as the View. You will also learn how to hide complex UI interaction inside tag libraries. The course will show you how it is possible to build a web application using these fundamental technologies, and how other frameworks are built.
Introduction Hi. This is Kevin Jones from Pluralsight, and this is the Java Web Fundamentals class. This is the introductory module; we'll be using this to cover some basics before we dive into the details of using the Servlet API and writing JavaServer Pages. Before we get into the details of building web applications using servlets and JavaServer Pages, we'll spend some time explaining why we believe it's important to understand these fairly low-level APIs, even if you are using a high-level framework such as Struts to build the applications yourselves. During the class we'll be using various tools such as Maven, Eclipse, and IntelliJ IDEA, and we'll take a look at those tools as part of this module. When we talk about Java web applications, we mean something very specific, and in this module, we'll take a look at exactly what it means to be a web application and how we create one. And then at the end of this module, we'll take a look at what's in the rest of the class, so apart from servlets and JSPs, there's details such as filters and listeners we need to cover.
The Expression Language Hi, this is Kevin Jones from Pluralsight. This is the module on the JavaServer Pages Expression Language. So I guess the first question is why do we have an Expression Language? Previous versions of JavaServer Pages relied on Java as the language that we can script with, so within the page itself we can add script tags, we can add expressions, but these were written in Java, and this has several problems. This makes it difficult to produce dynamic pages as the person writing the page has to know Java. So JavaServer Pages 2. 0 introduced this thing called an Expression Language, and the key point with the Expression Language is that it's very easy to use, so you don't have to be a programmer to fully use the Expression Language, you don't need to understand Java, you don't fully need to understand how programming languages work, so the Expression Language is very friendly towards page authors or designers. It gives these designers a limited form of scripting within the page, not so much that they can execute business logic, but certainly enough that they can manage the page layouts. One thing to be very aware of is that as the name implies, this is an expression language, so we can use expressions here, we can't use a full-blown language. So we don't have access to for loops, we don't have access to while loops. There are other ways of doing that within a JavaServer Page.