I agree on the "dont get it". I am not quite clear why there is so much
work involved in creating this tag lib.
In my mind, it seems as though the <tag.. /> is being replaced with java
code. This way, you dont have to populate your JSP pages with scriplets.
But, the mechanism for handling this seems odd. When I first heard of
taglibs, I thought it would be something simple, such as:
----------
taglib.jsp
----------
<taglib MyTagName>
<%
code here
%>
------------
somepage.jsp
------------
<%@ include file="taglib.jsp" %>
<MyTag />
Hello...
<MyTag>
<param name="this" value="this" />
</MyTag>
You see what I mean? I thought it was a way one developer could just write
a bunch of scriplet code that is into a JSP page. When included you just
simply use the tag, and pass parameters if need be, and thats that.
But, while I haven't looked at it in depth, it seems to me you have to
write classes, special code, etc to use a taglib. Ofcourse, that could be
because I have only seen some emails through here that show this kind of
stuf. It just seems to me the whole taglib thing is a great feature, but
overly complex for what its supposed to do. I want to design some tags that
a page design only needs to know the name, and what parameters to pass if any.
Anyone like to inform me of the real taglib truth? I can see it now, a
bunch of URLs to the java site. ;)
Kevin Duffey
Software Engineer
[EMAIL PROTECTED]
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
