Actually what you've described applies for any tag
lib. My approach is use Struts (or any tag lib)
selectively. For example, I would use <html:form> tag
but use HTML for the input elements. Instead of using
<bean:write>, I would use scriptlets to print the
information. Same goes for tags like
<logic:ifPresent>, <logic:ifNotPresent>, etc...
--- Rajan Gupta <[EMAIL PROTECTED]> wrote:
> Has anybody used Struts in a largescale application
> and witnessed
> performance issues. It seems to me that the cost of
> creating & destroying
> tags in a JSP page would create a lot of overhead on
> the JVM. By putting
> all HTML elements as tags would there be not a
> significant overhead of
> creating & destroying the tags. Of course the
> destroying would be handled
> by the garbage collector, but that could get
> significant.
> If all HTML code are tags, simple IF-ELSE statements
> are also tags and
> typically you could have more than 2-5 IF statements
> in a page.
>
> Is there some type of optimization built in struts
> to handle it or I am
> missing something in my understanding.
>
> Thx in advance for your responses.
> Rajan
>
>
__________________________________________________
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
