Obviously it's an architecture choice.
With the <jsp:include tag> you can access any beans placed within the
request using a <jsp:useBean> tag, but the dynamic content produced by it is
inserted into the calling page at the point where the <jsp:include> tag
occurs however, you cannot modify the headers.
Taglibs have many advantages. Taglibs have access to all objects available
to jsp pages and can be used to modify the response generated by the calling
page. They can communicate with one another and can be nested. I think this
gives you far more flexibility.
Justy
----- Original Message -----
From: "Muhammad Asif" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 13, 2001 10:39 PM
Subject: TagLibs Vs <jsp:include>
hi all,
Normally tag libs are used to hide common functinality in classes and making
our jsp page clean(i.e. free from scriplets). Same can be acheived by
<jsp:include>.
what is best situation to use either one or other?
What are advantages of using taglibs over jsp:include?
===========================================================================
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
