I see the dual--approach presented by JSP to be one of its strongest points.
As has been noted, TAGS can't do everything. However, they can do a lot. And
while maybe there's room for one or two more - I would introduce too much
more in the way of flow control or other programmatical issues, as the
quickly confuse non-programmers.
Here we use TAGS where we can because we have a pretty clean seperation of
roles in our group - Java coders write beans and servlets which get used by
the HTML designers through JSP display tags. Where TAGS can't do what the
designers want we step in and put it some scriptlet code. Then either we
(the programming team) become the new owners for that front-end or content,
or we have just tell them to "ignore this code here" and hope they don't
break it.
This scheme works pretty well for us, and why I don't know that creating a
bunch of new TAGS would hurt anything (I mean you don't HAVE to use them!),
I don't see how it really helps too much either.
--
Duane K. Fields
[EMAIL PROTECTED]
Sr. Internet Systems Engineer
Tivoli Systems, Inc.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
