> [mailto:[EMAIL PROTECTED]]
> > Enviado el: martes 26 de marzo de 2002 0:37
>
> Nice to hear that, one comment, there is a
> jakarta-tomcat-jasper
> repository with code Costin and Mel did some time
> ago as an initial
> effort to refactor the 3.3 Jasper, i dont know which
> is the state of the
OK, that'd be easier. :) I'll give it a try.
Thanks for the suggestion.
> Date: Wed, 27 Mar 2002 14:59:00 -0800 (PST)
> From: [EMAIL PROTECTED]
> Subject: RE: [PLAN] New Jasper
> X-X-Sender: <[EMAIL PROTECTED]>
> To: Tomcat Developers List <[EMAIL PROTECTED]&
On Wed, 27 Mar 2002, Kin-Man Chung wrote:
> I checked out jakarta-tomcat-jasper briefly looked at the files there.
> I agree with you (and constin) that it can be used as a repository for
> jasper2.
>
> However, files and directory structures are too different from the one
> used in tomcat 4, an
and see if jasper2 should move in there.
Thanks for the suggestion.
> Date: Tue, 26 Mar 2002 15:04:16 +0100
> From: "Ignacio J. Ortega" <[EMAIL PROTECTED]>
> Subject: RE: [PLAN] New Jasper
> To: 'Tomcat Developers List' <[EMAIL PROTECTED]>, '
>> May be because of license of javacc ;-)
>
>That hasn't stopped Velocity from using it. But in any case, there
>was an announcement on the JavaCC list a couple of days ago
>that JavaCC will be open sourced over the next few months.
Excellent news ;-)
will the license allow its distribution in
on of custom tags). It is much easier
for a custom parser to just handle them as special cases.
> Date: Tue, 26 Mar 2002 08:17:12 -0600
> From: Bob Lee <[EMAIL PROTECTED]>
> Subject: Re: [PLAN] New Jasper
> To: Tomcat Developers List <[EMAIL PROTECTED]>, 'Kin-Man
On Tue, 26 Mar 2002, Louis Tribble wrote:
> Henri Gomez wrote:
>
> > May be because of license of javacc ;-)
>
> That hasn't stopped Velocity from using it. But in any case, there
> was an announcement on the JavaCC list a couple of days ago
> that JavaCC will be open sourced over the next few
Henri Gomez wrote:
> May be because of license of javacc ;-)
That hasn't stopped Velocity from using it. But in any case, there
was an announcement on the JavaCC list a couple of days ago
that JavaCC will be open sourced over the next few months.
Louis Tribble
--
To unsubscribe, e-mail:
JavaCC is owned by Sun. The license doesn't look any more restrictive than
that of javac.
Bob
- Original Message -
From: "GOMEZ Henri" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, March 26, 2002 8:18 AM
Su
ob Lee [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, March 26, 2002 3:17 PM
>To: Tomcat Developers List; 'Kin-Man Chung'
>Subject: Re: [PLAN] New Jasper
>
>
>Possibly very stupid question...
>
>Is there any reason not to use JavaCC on the JSP compiler? I know the
>gramm
: "'Tomcat Developers List'" <[EMAIL PROTECTED]>; "'Kin-Man
Chung'" <[EMAIL PROTECTED]>
Sent: Tuesday, March 26, 2002 8:04 AM
Subject: RE: [PLAN] New Jasper
> > De: Kin-Man Chung [mailto:[EMAIL PROTECTED]]
> > Enviado el: martes 26 de
> De: Kin-Man Chung [mailto:[EMAIL PROTECTED]]
> Enviado el: martes 26 de marzo de 2002 1:13
> Thanks for the pointer. I'll look at both places to see if there are
> codes/ideas I can borrow.
My comment was more geared toward the use of this repository, than to
reuse the code there, i think is
"Kin-Man Chung" <[EMAIL PROTECTED]> wrote:
> I also would welcome ideas or suggestion about what and how to make jasper
> better. Pier's is the first complain that I've heard about jasper
> translation perfromance. :-)
Not translation (I didn't explain myself right, was too late yesterday night
> On Mon, 25 Mar 2002, Kin-Man Chung wrote:
>
> > I have noticed that the current Jasper does a lot of string
manipulations
> > very slowly, e.g. there are unnecessary copying or concatenations, and
> > the uses of String where StringBuffer should be used. Hopefully I can
> > avoid all of these.
On Mon, 25 Mar 2002, Kin-Man Chung wrote:
> I wasn't really serious when I suggested that Jasper generates byte codes.
Xalan is doing that already ( actually XSLTC ), and it's not very
difficult since we generate quite simple code, unlikely to be optimized
by javac too much.
It'll work only f
> On Mon, 25 Mar 2002, Kin-Man Chung wrote:
>
> > I have noticed that the current Jasper does a lot of string manipulations
> > very slowly, e.g. there are unnecessary copying or concatenations, and
> > the uses of String where StringBuffer should be used. Hopefully I can
> > avoid all of these
an be improved to
the point that an user will notice, because the time spent in Jasper
is probably small compared with that spent in javac. Now if we could
have jasper generate byte code directly...
> Date: Mon, 25 Mar 2002 23:40:05 +
> From: Pier Fumagalli <[EMAIL PROTECTED]>
>
On Mon, 25 Mar 2002, Kin-Man Chung wrote:
> I have noticed that the current Jasper does a lot of string manipulations
> very slowly, e.g. there are unnecessary copying or concatenations, and
> the uses of String where StringBuffer should be used. Hopefully I can
> avoid all of these.
>
> But I
ue, 26 Mar 2002 00:47:12 +0100
> From: "Ignacio J. Ortega" <[EMAIL PROTECTED]>
> Subject: RE: [PLAN] New Jasper
> To: 'Tomcat Developers List' <[EMAIL PROTECTED]>, 'Kin-Man Chung'
<[EMAIL PROTECTED]>
> MIME-version: 1.0
> X-Priority
On Tue, 26 Mar 2002, Ignacio J. Ortega wrote:
> > De: Kin-Man Chung [mailto:[EMAIL PROTECTED]]
> > Enviado el: martes 26 de marzo de 2002 0:37
>
> Nice to hear that, one comment, there is a jakarta-tomcat-jasper
> repository with code Costin and Mel did some time ago as an initial
> effort to re
On Mon, 25 Mar 2002, Kin-Man Chung wrote:
> I have been doing it so far in my own sandbox. The reason for this is not
> to keep it a secret, but to avoid de-stablizing the current tomcat,
> since a lot of my early work was mainly experimental. There have
> been interests recently in making the
> De: Kin-Man Chung [mailto:[EMAIL PROTECTED]]
> Enviado el: martes 26 de marzo de 2002 0:37
Nice to hear that, one comment, there is a jakarta-tomcat-jasper
repository with code Costin and Mel did some time ago as an initial
effort to refactor the 3.3 Jasper, i dont know which is the state of th
"Kin-Man Chung" <[EMAIL PROTECTED]> wrote:
> I plan to put back the new japser source tree in a day or two. If anyone has
> comments, concerns, or objections, please let me know. Of course, anyone
> interested in contributing to the new jasper development is also welcome.
YES PLEASE :) It's qu
23 matches
Mail list logo