At 07:34 PM 5/25/00 +0100, Kevin Jones wrote:
>with tags a better way would be to have two tags, one that manages the data
>and one that controls the ouput, so you have this
>
><xx:dataTag>
> <xx:outputTag />
></xx:dataTag>
The problem with this is that by using the custom <xx:outputTag /> you end
up fragmenting your HTML output.
It therefore requires that someone (possibly not a JSP developer) would
need to know where the outputTag code resides in order to make HTML code
changes.
The first tag <xx:dataTag> makes sense as it removes Java logic - but the
second one probably opens problems with page maintenance.
I'd suggest leaving all the HTML in the JSP when at all humanly possible.
- vin
===========================================================================
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
