Hello, I've been assigned my first server-side java project. I'm to convert a current mod_perl/postgres app that delivers dynamic content using multi-templates. I've installed JRun (that's what we're using) and I'm reading the O'Reilly Servlets book and the Manning JSP book. I'm curious as the best architecture (JSP/Servlets?) for this conversion. We sell content and some clients use our current system where all the content is on our server and they set up a template so there page still matches their format. For example, if a user goes to http://www.ourhostname.com/view/xxx/yy/2, then view maps to the mod_perl script and we use the extra path into xxx for the client parameter, yy as the feature parameter and 2 is the day parameter (like http://www.ourhostname.com/view.pl?client=xxx&feature=yy&day=2). The proper template is read from the database (determined by both the client and feature code) and then custom tags are grepped out with the proper content. Some content rarely changes, like copyright info, etc, while the 'feature body' tag is replaced with the actual "dynamic content" using the day parameter to pull the right feature from the database (there is an archive of content). JSP seems logical since we're using custom tags, but I'm not sure if that would work with multi-templates in a database. I'm not really keen on creating a separate JSP index page for each client/feature combination either. Would servlets best suite my purpose? Thanks in advance. =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". Some relevant FAQs on JSP/Servlets can be found at: http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.html http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
