To make a long story short, the major difference is that with taglibs, all of the Java
code is "hidden" from the JSP developer inside the tag handler code. With Java Beans,
on the other hand, the basic interface is to use XML syntax to set and get properties,
but the JSP developer can still (and may need to) call bean methods directly from
within the JSP page.
So in cases where you want non-developers to write JSP pages for you, taglibs are
best. They simply need to learn the tag syntax and understand how to use the
libraries, but they need not write any Java code. In this way, JSP pages end up
looking very much like palin old HTML pages, which the non-programmer is more used to
writing.
Robert
-----------------------------------------------------------
Robert Burdick
Author, "Essential Windows CE Application Programming", John Wiley & Sons
Co-author, "Professional JSP, 2nd Edition", Wrox Press
[EMAIL PROTECTED]
(650)-917-8446 (Office)
(650)-906-3707 (Cell)
===========================================================================
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://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
