ote:
On Sun, 24 Nov 2002, Peter Lin wrote:
> Date: Sun, 24 Nov 2002 18:08:00 -0800 (PST)
> From: Peter Lin
> Reply-To: Tomcat Developers List
> To: Tomcat Developers List
> Subject: RE: [Jasper2] framework for tag optimization
>
>
>
> Yeah, I actually use that in some
On Sun, 24 Nov 2002, Peter Lin wrote:
> Date: Sun, 24 Nov 2002 18:08:00 -0800 (PST)
> From: Peter Lin <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: Tomcat Developers List <[EMAIL PROTECTED]>
> Subject: RE: [Jasper2] framework
Yeah, I actually use that in some places, but it is a bit harder to read with pages
that have a lot of tags. Actually, the whole page is tags with very little HTML and
everything that is text is in resource bundles.
Using that syntax doesn't really bother in when used sparsely, but with hund
On Sat, 23 Nov 2002, Peter Lin wrote:
> Date: Sat, 23 Nov 2002 20:25:52 -0800 (PST)
> From: Peter Lin <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: Tomcat Developers List <[EMAIL PROTECTED]>
> Subject: RE: [Jasper2] framewo
I sent the suggestion a while back to the expert group.
> AFAIK, the and other tags don't actually generate *any* output
> of their own -- the extra line breaks you are seeing are undoubtedly those
> you've put in the source JSP page itself.
Yes, I was referring to the spaces that are generat
On Sat, 23 Nov 2002, Peter Lin wrote:
> Date: Sat, 23 Nov 2002 12:36:50 -0800 (PST)
> From: Peter Lin <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: Tomcat Developers List <[EMAIL PROTECTED]>
> Subject: RE: [Jasper2] framework
So it would seam having a plugin framework wouldn't necessarily break conformance. On
the otherhand, I would still like to see the expert group to seriously consider making
plugin framework a standard feature of JSP compiler. Beyond performance, there are
other good reasons to do so.
For o
On Sat, 23 Nov 2002, Peter Romianowski wrote:
> Date: Sat, 23 Nov 2002 18:05:29 +0100
> From: Peter Romianowski <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: 'Tomcat Developers List' <[EMAIL PROTECTED]>
> Subject: R
On Sat, 23 Nov 2002, Peter Romianowski wrote:
> Date: Sat, 23 Nov 2002 15:22:15 +0100
> From: Peter Romianowski <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: 'Tomcat Developers List' <[EMAIL PROTECTED]>
> Subject: R
Peter Romianowski wrote:
If you think using it for JSTL is okay, why wouldn't it be
okay for other tag libraries? The same issues (if they are
issues) apply to JSTL, don't they?
I thought of it beeing done by the jasper-crew, i.e. being
part of "stock tomcat", so it could be assured that it
ea but I am not sure if such a thing would belong to "stock
tomcat".
anyway,
Peter
> Hans
>
> >>-Original Message-
> >>From: Peter Lin [mailto:[EMAIL PROTECTED]]
> >>Sent: Saturday, November 23, 2002 4:59 AM
> >&g
s? The same issues (if they are issues) apply to JSTL,
don't they?
Hans
-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED]]
Sent: Saturday, November 23, 2002 4:59 AM
To: Tomcat Developers List; Kin-Man Chung
Subject: Re: [Jasper2] framework for tag optimization
hey kin-
at in respect of performance.
Just my $0.02
Peter
> -Original Message-
> From: Peter Lin [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, November 23, 2002 4:59 AM
> To: Tomcat Developers List; Kin-Man Chung
> Subject: Re: [Jasper2] framework for tag optimization
>
>
>
Message-
> From: Peter Lin [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, November 23, 2002 4:59 AM
> To: Tomcat Developers List; Kin-Man Chung
> Subject: Re: [Jasper2] framework for tag optimization
>
>
>
> hey kin-man,
>
> that sounds great! I was actually thinking
hey kin-man,
that sounds great! I was actually thinking along those lines a while back, but
thought it was impracticle because the project I was working one didn't have enough
time to explore that approach.
when I was doing performance analysis of jasper1 with jslt and saw how bad the
perf
I am designing a framework in Jasper for enabling plugins that
work closely with Jasper to generate Java codes instead of calls
to tag handlers. The main idea is to take take JSTL tags, such as
${i}
and generates the Java codes
for (int i = 0; i <= 100; i++
16 matches
Mail list logo
