I think it depends on, what you're trying to achieve: If i remember it corrctly, the tags inside the jsp get inlined when the jsp is compiled: So the performance problem boils down to a problem of objectcreation and -deletion, which nowadays is handled quite good by most modern jvm. If you want to fetch labels from property-files, then the properties are cached in a per-jvm manner. If you really run into performance issues, i don't think they come from using taglibs but from the requirement to mix-in the labels dynamically (maybe to perform internationaliation or - even worse - based on user-rights or preferences): So maybe you should try to think of some sort of pre-processing (generating templates with the right labels in it and then using a simple template-engine or maybe even simple bean-tags(<%=..%>) to populate the pages.
And maybe you should have someeone think about the requirement for exposing ten thousands of users to 50 -100 elements on just one page - has to be a very special audience...;) ----- Original Message ----- From: "Bob Williams" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Tuesday, February 12, 2002 4:05 PM Subject: Re: help: <%>.. how do i convince them to learn JSP? > I have no problem being convinced that tags should be used for generating > complex items on a web page. The one concern I do have, relative to using > tags, is the extra processing required to generate simple things. I have > seen pages in industrial environments where the page may have 50-100 > elements displayed (and no this is not a problem with the design this is a > real application requirement!). Using a tag to generate labels and text > input boxes seems like it would add a significant compute load on a server > that is servicing 100's of people. The same situation applies when you are > dealing with pages with fewer elements, but are being served up to 1000's or > 10,000's of users. > > Does anyone have experience about computing resources required by tags in > these types of scenarios? > > bob > ----- Original Message ----- > From: "Sarah Farrell" <[EMAIL PROTECTED]> > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > Sent: Monday, February 11, 2002 9:48 PM > Subject: Re: help: <%>.. how do i convince them to learn JSP? > > > > > > Michael, > > > > Here's the best one I could find. > > > http://java.sun.com/blueprints/guidelines/designing_enterprise_applications/ > > web_tier/qanda/index.html > > > > There are some other ones on java.sun.com if you search for "JSP > presentation > > logic separate". > > > > Here's another one: > > http://java.sun.com/products/jsp/ > > > > > > > > P.S. Please don't cross-post to multiple jakarta lists. > > > > > > > > At 07:34 PM 2/11/2002 -0800, you wrote: > > >long before server pages or servlets existed i was > > >writing these C++ template based systems with CGI > > >so i could do my best to separate content generation from programming > > >logic... > > > > > >i'm a consultant and this company made me lead on my first JSP/Servlet > based > > >project, > > >i was really excited to get involved with JSP tag libraries. > > > > > >but when i got into the code base IT'S ALL .jsp files with > > >TONS of Java scriptlets! it's nasty. if/else blocks several hundred > lines > > >long. > > >the developer i took this over from > > >thinks there is no reason to do it any other way. tags? why use tags? > > > > > >i am asking for input/references on why you want to keep the scriptlets > <%> > > ></%> > > >out of the JSP files. every time i try to make a point-- maybe > > >i'm just not being eloquent enough... > > > > > >on another note: is it really model 2 if a JSP is processing the request? > > >i don't think it is, even if your entire JSP is just some java code > > >wrapped with a scriptlet tag.. (yuk). > > > > > >thanks for input. > > >--Michael > > > > > > > > > > > > > > > > > > > > > > > >-- > > >To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > >For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
