this is (probably) a "there is no right answer" question about design: when designing a site that will have a standard header, is it considered better form to have a Header object that will get instantiated on every page just so you can call a method that does some processing/database hits and then writes the header html, or is it better to have a class with a bunch of static methods that handle this kind of thing (dynamic headers, footers, breadcrumbs, etc.). btw, i'm using jsp. or maybe there's another way altogether... thanks! ed
Here's a solution 1) Create a JavaBean that handles the database. 2) Create a file header.jsp that uses the bean and displays the info. 3) In all other files include the header.jsp at the required place. use the include directive <%@ include file='header.jsp' %> or use the include action <jsp:include page='header.jsp' />
Joined: Nov 29, 2001
that sounds good, but what if the header builds a breadcrumb that is based on a node id on the page that does the including? is there a way to get the bean some information it needs to build the correct header?