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 just figured it out. In JSTL's standard.jar it contains a copy of the
.tld files. Even though I added varStatus as an attribute to the copy
in /WEB-INF/x.tld, it was going by the copy in the jar.
Once I deleted the tld file in the jar, it worked fine. why the change
in 4.1.10?
peter lin
On Thu, 27 Jun 2002, Jan Luehe wrote:
> > And I would bet most jsp implementations in use are doing exactly
> > what jasper1 is doing - and changing this will create big problems
> > ( while still beeing non-compiant with the spec, and completely
> > counterintuitive )
>
> But there also could b
Costin,
> > > - I have a
> > >
> > >
> > > The generated code is:
> > > a = (java.lang.Object) pageContext.findAttribute("a");
> > > a = (java.lang.Object) pageContext.findAttribute("a");
> > > a = (java.lang.Object) pageContext.findAttribute("a");
> > > ( i.e. 3 times the same line ).
> >
On Thu, 27 Jun 2002, Jan Luehe wrote:
> Costin,
>
> > - I have a
> >
> >
> > The generated code is:
> > a = (java.lang.Object) pageContext.findAttribute("a");
> > a = (java.lang.Object) pageContext.findAttribute("a");
> > a = (java.lang.Object) pageContext.findAttribute("a");
> > ( i.e. 3
Costin,
> - I have a
>
>
> The generated code is:
> a = (java.lang.Object) pageContext.findAttribute("a");
> a = (java.lang.Object) pageContext.findAttribute("a");
> a = (java.lang.Object) pageContext.findAttribute("a");
> ( i.e. 3 times the same line ).
>
> Not a bug, but strange.
this t
On Wed, 26 Jun 2002, Kin-Man Chung wrote:
> That's true, but the value of those variables are still synchronized
> with the corresponding pageContext attributes at the locations
> specified by the spec, so using these variables before they are
> synchronized is meaningless.
>
> The spec as is to
> > > - in the same case, the 'a' variable is declared at the top
> > > of the file, even if it is AT_END. That brakes previous
> > > that used the 'a' id. I believe this is a bug.
> >
> > According to the spec, the scope of an AT_END variable spans
> > from the end element of the tag exposing
On Wed, 26 Jun 2002, Jan Luehe wrote:
> > - in the same case, the 'a' variable is declared at the top
> > of the file, even if it is AT_END. That brakes previous
> > that used the 'a' id. I believe this is a bug.
>
> According to the spec, the scope of an AT_END variable spans
> from the end el
I tried again, and it worked. There is still one error ( i.e. a page that
worked before but no longer does ), but that may be legitimate.
2 more problems:
- I have a
The generated code is:
a = (java.lang.Object) pageContext.findAttribute("a");
a = (java.lang.Object) pageContext.findAttribut
On Mon, 24 Jun 2002, Kin-Man Chung wrote:
> With the Jan's patch last Friday, jasper 2 should handle those cases
> that used to work for japser1, as well as those those that cannot be
> handled by jasper1. If this is not the case, please let me know.
The current failing case is ( used to work f
> My problem is that code that worked with jasper1 no longer works with
> jasper2.
>
> And I believe the use case is valid and within the spec, and quite
> common.
>
> The latest failure is just 2 iterate tags and a condition tag -
> I think it should work.
>
> Costin
>
With the Jan's pat
On Mon, 24 Jun 2002, Kin-Man Chung wrote:
> > > Use of scripting varibles in nested tag never work before, so obviously
> > > no body uses it much. I think the whole scripting variable in JSP1.2 is
> > > poorly designed, and not well understood.
> >
> > The failures are from an app that worked
Costin,
>
> On Fri, 21 Jun 2002, Kin-Man Chung wrote:
>
> > Use of scripting varibles in nested tag never work before, so obviously
> > no body uses it much. I think the whole scripting variable in JSP1.2 is
> > poorly designed, and not well understood.
>
> The failures are from an app that w
Costin,
> How do we deal with nested tags of different type ? I don't have
> a test case, but I assume someone may have a NESTED tag
> 'foo' in 2 different tags, with different declared types ( String and
> Integer ). The current generator seems to not create { },
> and I'm not sure how this
Costin,
> > If those variable declaration problems are fixed, I'll release a new
> > 4.1.6 milestone as soon as I can fix the JNDI problems.
>
> Not yet...
>
> I attached the failed jsp.
>
> Costin
>
> [...]
>
> <%@ page language="java
On Fri, 21 Jun 2002, Jan Luehe wrote:
> the current approach should be able to handle a NESTED 'foo' in 2
> different tags, with different declared types, as long as one tag
> isn't nested inside the other. The current approach will generate code
> like this:
>
> {
> Integer foo;
> }
>
On Fri, 21 Jun 2002, Kin-Man Chung wrote:
> Use of scripting varibles in nested tag never work before, so obviously
> no body uses it much. I think the whole scripting variable in JSP1.2 is
> poorly designed, and not well understood.
The failures are from an app that worked perfectly fine with
Costin,
> I'm a bit worried here - most of the stuff is pretty basic and
> common use of tags. Watchdog and the test suite was supposed
> to detect that withou any problems.
>
Use of scripting varibles in nested tag never work before, so obviously
no body uses it much. I think the whole scri
Thanks, I'll try it out.
I'm a bit worried here - most of the stuff is pretty basic and
common use of tags. Watchdog and the test suite was supposed
to detect that withou any problems.
I'll vote for 'alpha' status for the next build,
and I hope more people will check their apps against it -
On Fri, 21 Jun 2002, Remy Maucherat wrote:
> If those variable declaration problems are fixed, I'll release a new
> 4.1.6 milestone as soon as I can fix the JNDI problems.
Not yet...
I attached the failed jsp.
Costin
package JspServ;
import javax.servlet.*;
import javax.servlet.http.*;
Jan Luehe wrote:
> Hi Costin,
>
>
>>But there is still a problem - now if you have:
>>
>>
>>
>>
>>
>>
>>( i.e. the same variable name ), it will fail with duplicated declaration,
>>the code will be:
>> Object i;
>> ...
>> Object i;
>>
>>( id is nested ).
>
>
> The above code f
Hi Costin,
> But there is still a problem - now if you have:
>
>
>
>
>
>
> ( i.e. the same variable name ), it will fail with duplicated declaration,
> the code will be:
>Object i;
>...
>Object i;
>
> ( id is nested ).
The above code fragment compiles fine for me.
I
Many thanks Jan and Kin-Man.
But there is still a problem - now if you have:
( i.e. the same variable name ), it will fail with duplicated declaration,
the code will be:
Object i;
...
Object i;
( id is nested ).
As I mentioned, the 4.1.4 milestone doesn't have this pro
Hi Costin,
> More info:
>
> The page is:
>
> <%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>
>
>
>
> Foo
>
>
>
> I get:
>
> a$jsp.java:75:25:75:25: Error: No entity named "id2" was found in this
> environment.
>
> And the generated code is:
> .
om directly ).
Costin
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: 18 June 2002 06:44
> > To: Tomcat Developers List; Kin-Man Chung
> > Subject: Re: Jasper2: serious problem with tag declarations
> >
>
> Date: Tue, 18 Jun 2002 11:04:10 +0100
> From: [EMAIL PROTECTED]
> Subject: RE: Jasper2: serious problem with tag declarations
> To: [EMAIL PROTECTED]
> MIME-version: 1.0
> X-MIMEOLE: Produced By Microsoft Exchange V6.0.5762.3
> Content-transfer-encoding: quoted-prin
for a few extra {}'s?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 18 June 2002 06:44
To: Tomcat Developers List; Kin-Man Chung
Subject: Re: Jasper2: serious problem with tag declarations
On Mon, 17 Jun 2002, Kin-Man Chung wrote:
> Costin,
>
>
[EMAIL PROTECTED] wrote:
> On Thu, 13 Jun 2002, Remy Maucherat wrote:
>
>
>>[EMAIL PROTECTED] wrote:
>>
>>>There are few bugs in jspc, mostly related with the generation of the
>>>class name and the mangling.
>>
>>Ooops, sorry, I thought I got it right. At least for the examples
>>webapp, it
On Thu, 13 Jun 2002, Remy Maucherat wrote:
> [EMAIL PROTECTED] wrote:
> > There are few bugs in jspc, mostly related with the generation of the
> > class name and the mangling.
>
> Ooops, sorry, I thought I got it right. At least for the examples
> webapp, it did appear to work good. It is qu
[EMAIL PROTECTED] wrote:
> There are few bugs in jspc, mostly related with the generation of the
> class name and the mangling.
Ooops, sorry, I thought I got it right. At least for the examples
webapp, it did appear to work good. It is quite hard to un-spaghetti the
code without beaking anyth
On Wed, 12 Jun 2002, Ian Darwin wrote:
> For one thing I don't think a LOT of people actually specify the buffer size
> (of course those who DO will jump in to prove me wrong, and those who
> don't will remain silent :-)).
>
> For another, memory is getting bigger quickly, and having sizes of th
On June 11, 2002 10:19 pm, you wrote:
> There are plenty of JSP1.1 pages out there, this will require people to
> rewrite the pages just to add a 'kb' suffix ( which is pretty weird
> by itself, almost everything else uses k, and is redundant - if
> the size can only be specified in kb, there is n
On Tue, 11 Jun 2002, Bill Barker wrote:
> > The JSP1.1 ( and previous jaspers ) didn't require that ( AFAIK ), so
> > that would brake backward compat. It'll also brake a lot of pages.
> >
>
> Unfortunately, Kin-Man is correct that the kb is required in JSP-1.2.
>
>
> The size can only be spec
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, June 11, 2002 4:59 PM
Subject: jasper2: @page buffer syntax
> One more ( today is my jaspers day :-):
>
> in Validator.PageDirectiveVisitor, there is a check for the syntax of
Glenn,
Thanks a lot for adding the '<%@ include file' support! I just signed up
last night to be on this mailing list because I was going to start this.
- Abe
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of Glenn Nielsen
Sent: Monday, May 06, 2002 12:0
[EMAIL PROTECTED] wrote:
>
> I had problems with the new compiler / runtime environment though (for ex,
> the include example doesn't work, and the admin webapp can't compile), so
> it's not ready yet.
>
The include example is wrong in that it includes a page directive
<%@ page buffer="5"
> > I think I've done the part on the container improvements (at least, the
> > additional tweaks won't bring any big performance increase now); the
rest
> > seems up to the compiler.
> >
> > Remy
> >
>
> Tomcat 4 is still significantly slower than tomcat 3, based on some
> performance tests Prasa
Good for you, Remy!
> Actually, I've already done the optimization for the runtime and it is very
> significant for simple pages (see my commits last week); when the page does
> run, it does it very fast now. There's no hotspot left in the runtime
> (according to OptimizeIt; of course, it won't h
> I am opening the discussion in [EMAIL PROTECTED], if you don't
> mind. I think there are others who may be interested in the topic.
>
> jasper2 is in jakarta-tomcat-jasper. You'll need to build
jakarta-tomcat-4.0
> first, and then jasper2. It just drops the jar files into tomcat build
area.
>
-
From: Kin-Man Chung [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 03, 2002 12:58 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Jasper2
I am opening the discussion in [EMAIL PROTECTED], if you don't
mind. I think there are others who may be interested in the topic.
jasper2
On Wed, 3 Apr 2002, Kin-Man Chung wrote:
> It's great that you are doing performance evaluation for different versions
> of tomcat. Can your jstl run in tc3 and tc4 without change? Can we
> separated performance attributed to containers as opposed to those attributed
> to jasper? For those jas
I don't mind. I plan on writing a clean site from scratch for doing the
performance evaluation. The test pages I used to perform the previous
tests will only work for tomcat 4.0. Which is why I plan on writing a
new demo site from scratch for my own testing purposes.
My existing test pages are
I am opening the discussion in [EMAIL PROTECTED], if you don't
mind. I think there are others who may be interested in the topic.
jasper2 is in jakarta-tomcat-jasper. You'll need to build jakarta-tomcat-4.0
first, and then jasper2. It just drops the jar files into tomcat build area.
Ignore jas
58 matches
Mail list logo
