Lecture11
- 1. Server-side Web Programming Lecture 11: Modular Web Programming
- 2. Including Static Resources Pages on same site should have same layout Site identifiable to user User knows where to look for major components (navbar, etc.) Example: CSS style sheets to unify appearance Example: All pages on site have same navigation bar
- 3. Including Static Resources Bad idea: copy and paste html for navigation bar into each file If change layout, must modify every file on the site Better idea: “include” single file containing navigation bar into every page on site Just need to modify single file Done client side with frames navbar.htm JSPs included in
- 4. Server-side Includes Can use web container to include files Server page being generated for response Just include files Syntax: <%@ include file=" relative file location " %> For example: <%@ include file=“navbar.html" %>
- 5. Including Dynamic Resources Can break dynamically generated JSP into separate files Easier to develop and maintain as group Configuration.jsp Information.jsp CreditCard.jsp
- 6. Including Dynamic Resources Syntax: <jsp:include page=" relative file location " />
- 8. Including Dynamic Resources Why different syntax? Steps in creating response: JSP translated into an equivalent servlet. Servlet is compiled. The doGet or doPost method of servlet run to create response page <%@ include file=“ … " %> executed once when compiled More efficient <jsp:include page=“ … " /> must be executed every time page called Will generate different html each time based on user parameters <%@ include file=””%> <jsp:include page=“” />