RE: trade-off
They are used in the Template Example application, if you want to see a set in action. Another templating approach is Components Library for building JSP views by Cedric Dumoulin at < http://gauss.ficsgrp.com/cdm/index.html >. *** REPLY SEPARATOR *** On 1/17/2001 at 3:06 PM Deadman, Hal wrote: I know the pages that use template tags are slow the first time you hit them because there are normally several jsps that need to get compiled. After that I would think it would be the same performance-wise as a jsp that does lots of jsp:includes. Has anyone tried to use struts-templates in production? I am starting to use them for a bench project in order to guage their value so I can't really speak to their performance.
RE: trade-off
>Speaking of includes, the following sentence in the documentation is >misleading/wrong: >From /struts-documentation/building_view.html I'll take care of that, I'll also take care of the other documentation problem with data sources. Thanks
RE: trade-off
I know the pages that use template tags are slow the first time you hit them because there are normally several jsps that need to get compiled. After that I would think it would be the same performance-wise as a jsp that does lots of jsp:includes. Has anyone tried to use struts-templates in production? I am starting to use them for a bench project in order to guage their value so I can't really speak to their performance. Speaking of includes, the following sentence in the documentation is misleading/wrong: >From /struts-documentation/building_view.html The include directive (<%@ include file="x" %>) is processed when the JSP page is compiled. It is useful when you are including HTML code that will not need to change at request time. It treats the text being included as static text, much like the #include directive in C or C++. An <%@ include file="x" %> directive can include a file that contains java code or jsp tags. The code in the included file can even reference variables declared earlier in the outer jsp page. The code is inlined into the other jsp before it is compiled so it can definately contain more than just HTML. Hal -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 17, 2001 1:27 PM To: Struts List Subject: Re: trade-off The template tags in the Struts library seem a bit pokey, but there's a lot going on there (reads one file, then merges from another). I don't think alot of applications actually use these tags much. I believe that any JSP is suppose to compile down to a single servlet class file. The custom tags are just alternate ways to call subroutines. If you check your work directory, you'll see that a number of automatic Java files might be generated for a given JSP, but they resolve to a single class. Struts is also fine with distributing precompiled JSPs, which can eliminate the cycles it takes the container to check to see if the JSP needs to be recompiled. *** REPLY SEPARATOR *** On 1/17/2001 at 9:43 AM John Hunt wrote: Hi What do you think is the over-head in using struts tags in terms of performance? ( all tags in general ) And let us say we use a template for a page which has a header, a side bar, a footer, a content. Each of this gets commpiled into a class and thus a single page is converted into a set of classes ( r these a set of servlets )? Doesnt it slowdown when compared to a single servlet just outputting the stuff??? Thanks Hunt __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
Re: trade-off
The template tags in the Struts library seem a bit pokey, but there's a lot going on there (reads one file, then merges from another). I don't think alot of applications actually use these tags much. I believe that any JSP is suppose to compile down to a single servlet class file. The custom tags are just alternate ways to call subroutines. If you check your work directory, you'll see that a number of automatic Java files might be generated for a given JSP, but they resolve to a single class. Struts is also fine with distributing precompiled JSPs, which can eliminate the cycles it takes the container to check to see if the JSP needs to be recompiled. *** REPLY SEPARATOR *** On 1/17/2001 at 9:43 AM John Hunt wrote: Hi What do you think is the over-head in using struts tags in terms of performance? ( all tags in general ) And let us say we use a template for a page which has a header, a side bar, a footer, a content. Each of this gets commpiled into a class and thus a single page is converted into a set of classes ( r these a set of servlets )? Doesnt it slowdown when compared to a single servlet just outputting the stuff??? Thanks Hunt __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
trade-off
Hi What do you think is the over-head in using struts tags in terms of performance? ( all tags in general ) And let us say we use a template for a page which has a header, a side bar, a footer, a content. Each of this gets commpiled into a class and thus a single page is converted into a set of classes ( r these a set of servlets )? Doesnt it slowdown when compared to a single servlet just outputting the stuff??? Thanks Hunt __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/