Lecture 11
Lecture 11
Web Programming
Lecture 11:
Modular Web Programming
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
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
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" %>
Including Dynamic Resources
• Can break dynamically generated JSP into separate files
– Easier to develop and maintain as group
Configuration.jsp
Information.jsp
CreditCard.jsp
Including Dynamic Resources
• Syntax:
<jsp:include page="relative file location" />
Sample Included Page
Including Dynamic Resources
• Why different syntax?
• Steps in creating response:
1. JSP translated into an equivalent servlet.
2. Servlet is compiled.
3. The doGet or doPost method of servlet run to create response page