Re: JSTL EL parser pool?

2002-03-22 Thread peter lin
Here are some thoughts Shawn Bayern wrote: > > On Fri, 22 Mar 2002, peter lin wrote: > > > Interesting thought, Peter. > > Given that instantiating an Evaluator object involves no specific logic on > construction, the only cost of not having a pool is that of object > creation itself, wh

RE: Grouped Output

2002-03-22 Thread Shawn Bayern
On Fri, 22 Mar 2002, Zvolensky, Thomas J {PDBI~Nutley} wrote: > My principal problem is to avoid repeating the "grouped" column item > on every detail line on the resulting web page. I only want it to > appear on the first line and list details below it. Can you explain > how the "group by clau

RE: Grouped Output

2002-03-22 Thread Zvolensky, Thomas J {PDBI~Nutley}
Shawn, My principal problem is to avoid repeating the "grouped" column item on every detail line on the resulting web page. I only want it to appear on the first line and list details below it. Can you explain how the "group by clause" can help with this formatting? Thanks. -Original Mess

Re: JSTL EL parser pool?

2002-03-22 Thread Shawn Bayern
On Fri, 22 Mar 2002, Shawn Bayern wrote: > The evaluator keeps a static cache of values, so literally the only > benefit of pooling our interpreter instances would be to save the > instantiation itself, which should take about ten low-level instructions > on a modern JIT. (That is, the evaluator

Re: JSTL EL parser pool?

2002-03-22 Thread Shawn Bayern
On Fri, 22 Mar 2002, peter lin wrote: > I've been doing benchmarks with JSTL on some dynamic pages and noticed > under medium & heavy load 4-64 concurrent connections, the performance > degrades rapidly. I looked at ExpressionEvaluatorManager and it looks > like it doesn't create a pool of parse

Re:

2002-03-22 Thread Shawn Bayern
On Fri, 22 Mar 2002, John Baker wrote: > Is it possible to get at request.getContextPath() like this: > > 'contextPath' in that expression is a scoped attribute. If you want to access properties of the HttpServletRequest object itself, you need to do so through 'pageContext'. That is: ${p

taglibs-user@jakarta.apache.org

2002-03-22 Thread John Baker
Is it possible to get at request.getContextPath() like this: Thanks! -- John Baker, BSc CS. Java Developer, TEAM/Slb. http://www.teamenergy.com Views expressed in this mail are my own. -- To unsubscribe, e-mail: For additional commands, e-mail: