Hi Louis, It very much depends on your internal development process. It very much depends also on what you call "presentation". If you replace Java code by equivalent programming constructs which just have a different (tag) syntax, then your designer still has to be doing programming and he/she still has to understand the UI logic of the application. So the only benefit will be the different syntax (Java vs XML tags). As a general advice, all logic decisions should be made outside of the JSP page so that your designer is only dealing with formatting. Displaying a list of options from the database is a good candidate for tags yes.
John > Hi everyone, > > Some days ago I posted a message about the better way to separate logic form >presentation in a JSP, and some people suggested using taglibs. I decided to use >them, but have some doubts. > > For instance, when should I use a custom tag and how? Should I program all the logic >in tags so the designer won't mess with Java code, or he should know at least some >Java to program loops or decisions? > > I need to display a list of options which I get from a database, should I use >taglibs here? > > Sorry for asking too many questions in a single message, but it would be first time >I use taglibs and there are some things that I still don't have clear. > > Thanks again for your help! > > Luis Javier > > > > -- _______________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
