What I do is that I make all my links point back to my servlet with something like serMyServlet?mode=about then I have the servlet process the "mode" parameter and find the "about" section. This then runs a method which returns a JSP to the browser.
Architecture is always MVC, Classes doing processing and DB access fronted by a single servlet which spits out JSPs. Andoni. ----- Original Message ----- From: "Kevin Andryc" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Friday, February 21, 2003 2:31 PM Subject: Slightly Off Topic: Web Site Content > Hello, > I have been doing web programming for quite some time but what I have > yet to figure out is the best way to handle web site content. For example, > if I want to create a web sire with a vast number of pages, I would like to > have it easily maintained such that if a link changes in my navigation bar, > the rest gets updated rather than picking through every page. What is the > best way to do this? Do you guys use JSP pages and have the navigation or > content stored in a database and then retrieved by the JSP? How about > architecture? Are there any good books on this? Any help would be great. > > Sincerely, > Kevin > > Kevin Andryc > Web Systems Engineer > MISER > http://www.umass.edu/miser/ > Phone: (413)-545-3460 > [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
