One issue not really discussed is the performance
aspect of using tags. Looking at the generated Java
source from a JSP, a single tag can be expanded into 5
or more lines of Java code. For a simple tag like
"ifNull", I would think using scriptlets with a if
statement will lead to better performance (although
I've NOT done any timing measurement).
Just my two cents.
--- David Geary <[EMAIL PROTECTED]> wrote:
> Of course, the functionality in the JSP page listed
> above could be
> implemented as a custom tag. Whether you implement
> JSP pages or custom tags
> is largely a matter of taste. Custom tags are a
> little more difficult to
> develop, but they are easier for page authors to
> use. JSP components are
> easier to develop, but they are a little more
> difficult for page authors to
> use because they must be included.
>
> > Just wondering before I embark on my project, if
> it's worth including the
> > design of any extra tags, or just doing the things
> I want in <% %> ...
>
> The bottom line is twofold: reuse and division of
> labor. You can't reuse
> scriptlets buried in a JSP page, but you can reuse
> custom tags or JSP
> components. If you're on a large project with
> software developers and page
> authors, ideally you'd like the page authors to use
> tags implemented by
> developers. This helps maintain a division of labor
> where software developers
> and page authors can work in parallel, with few
> dependencies.
>
>
> david
>
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
