Re: Jasper TCKing

Yoav, Thank you for the offer. It's certainly welcome. We have TCK grants for these APIs at Apache, and have had them for years. (In fact, the ASF has TCK rights from Sun for virtually every API out there ;)) But as you've noted, it's a time-consuming task, and in general we gladly welcome ex

Re: Jasper TCKing

Rick, Thank you for the offer. It's certainly welcome. We have TCK grants for these APIs at Apache, and have had them for years. (In fact, the ASF has TCK rights from Sun for virtually every API out there ;)) But as you've noted, it's a time-consuming task, and in general we gladly welcome exter

Re: Jasper and external entities parsing

Henri Gomez wrote: From what I see in the 5.5.8 code the external entities cannot be resolved since we provide an InputSource to the documentBuilder in ParseUtils : private void processWebDotXml(ServletContext ctxt) throws JasperException { InputStream is = null; try {

Re: Jasper-compiler woes

broken... Thanks again, Martin - Original Message - From: "Sriram N" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Sunday, November 14, 2004 11:19 PM Subject: Re: Jasper-compiler woes > > --- Laconia Data System

Re: Jasper-compiler woes

I was using JspC from jasper-compiler.jar I'll try again with JDT Compiler Thanks, Martin- - Original Message - From: "Sriram N" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Sunday, November 14, 2004 11:19

Re: Jasper-compiler woes

--- Laconia Data Systems <[EMAIL PROTECTED]> wrote: > All- > > I cannot get jasper compiler to work from Ant > has this been fixed with any version of Tomcat 5 jasper-compiler.jar? > If so where is the patch? Here's how I have used Ant 1.6.x with the JDT compiler. ant -Dbuild.compiler=org.ecli

Re: jasper compiler problem & semi-ready patch

Martin, thanks for reporting the issue, and proposing a patch. Your patch is consistent with this recommendation in the class comment of java.net.URLConnection: Calling the close() methods on the InputStream or OutputStream of an URLConnection after a request may free network resources asso

Re: Jasper used for Tomcat 4.0.6

The code for Jasper in 4.0.x is in the module jakarta-tomcat-4.0. > Date: Thu, 30 Oct 2003 14:51:13 -0600 > From: Ken Sipe <[EMAIL PROTECTED]> > Subject: Jasper used for Tomcat 4.0.6 > To: [EMAIL PROTECTED] > X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 > Importance: Normal > X-Priorit

Re: Jasper & Cocoon's Eclipse Compiler Plugin

On Thu, 31 Jul 2003, Remy Maucherat wrote: > Jasper uses Ant and that was a rather painful switch which needed lots > of testing to start working fine. You should be able to use EDT through Ant. > I'm against what you propose (lots of pain, no gain). You are right. With some afterthought, I was a

Re: Jasper & Cocoon's Eclipse Compiler Plugin

[EMAIL PROTECTED] wrote: Hi, I'm experimenting with embedding Jasper/JSP 2.0 into production servlet 2.3 containers / JSP 1.2. That works surprisingly well, using an alternative lib directory and an additional classloader. (I want to run tagfiles in Websphere,Dynamo,... before 2005.) Anwyay, one o

Re: Jasper & Cocoon's Eclipse Compiler Plugin

On Wed, 30 Jul 2003, Glenn Nielsen wrote: > Plugging in a different javac compiler if it works better may be > of iterest. The only way for the tomcat developer community to > determine this is to submit a patch so that it can be evaluated. Alright. I'll come up with one. I was only wondering if

Re: Jasper & Cocoon's Eclipse Compiler Plugin

[EMAIL PROTECTED] wrote: Hi, I'm experimenting with embedding Jasper/JSP 2.0 into production servlet 2.3 containers / JSP 1.2. That works surprisingly well, using an alternative lib directory and an additional classloader. (I want to run tagfiles in Websphere,Dynamo,... before 2005.) Anwyay, one o

Re: Jasper: Error running javac.exe compiler (tc4.1.24)

im on Windows XP pro, jdk1.4.1_02, tomcat 4.1.24. my guess would be the classpath is too long and gets truncated hence the "C:\Tomc?". thois would be a good point for ANT-guys! because they could use the CLASSPATH-env-variable instead, so the command-line would stay short. "[javac] Since fork is

RE: Jasper: Error running javac.exe compiler (tc4.1.24)

Thomas, Is javac.exe in Tomcat's path? My guess is that Ant can't find javac.exe -Chad Johnson (you may be better off asking this in tomcat-user) -Original Message- From: Thomas Heller [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2003 10:05 AM To: [EMAIL PROTECTED] Subject: Ja

Re: Jasper, JMX and JSR77

I have looked at JSR 77, but not in depth. I am all for instrumenting Tomcat using JMX where it makes sense. And will help when/if I have time. Glenn Costin Manolache wrote: JSR77 defines a certain model - in particular a WebModule must include an attribute "servlets[]" that lists all the serv

Re: Jasper, JMX and JSR77

Costin Manolache wrote: JSR77 defines a certain model - in particular a WebModule must include an attribute "servlets[]" that lists all the servlets in the webapp, and it also requires on JMX mbean per servlet. ( tomcat uses that to provide all kind of performance and statistical info ). The pro

Re: Jasper and big jsp files ( not working !! )

On Tue, 7 Jan 2003 20:15:22 +0100, "Holger Brozio" <[EMAIL PROTECTED]> escreveu : > De: "Holger Brozio" <[EMAIL PROTECTED]> > Data: Tue, 7 Jan 2003 20:15:22 +0100 > Para: "Tomcat Developers List" <[EMAIL PROTECTED]> > Assunto: Re: Jasper

Re: Jasper and big jsp files ( not working !! )

Hi, i have reported this as a bug before, see http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14359 for more details, but i have no real solution for this now. Is this also your problem? One workaround may be to split the jsp files and include the content by a jsp:include? Holger - Origi

Re: Jasper 2 Synchronized JSP compiles

Glenn Nielsen wrote: I have some ideas on how invoking the javac compiler for compiling JSP pages can be improved. Currently Jasper 2 uses ant to do compiles from within Tomcat which are synchronized. There are currently several problems. 1. The known javac memory leak. 2. JSP page compiles

Re: Jasper 2 Synchronized JSP compiles

Performance-wise, wouldn't doing javac compilation in another process be much worse than synchronized javac, at least for systems with small number of processors? It would nice if we can have some numbers for comparision. I know javac used to have memory leak, but is it still true for modern comp

Re: Jasper 2 Synchronized JSP compiles

+1, good idea ! Costin Glenn Nielsen wrote: > I have some ideas on how invoking the javac compiler for compiling JSP > pages can be > improved. Currently Jasper 2 uses ant to do compiles from within Tomcat > which are synchronized. > > There are currently several problems. > > 1. The known ja

Re: Jasper Classloader question

John Trollinger wrote: > I am trying to access the jasper class loader directly. I want to do > this so that I can get a jsp class file out of it at runtime vs having > to do a jsp:include to call the jsp. I am having a little trouble > getting through the jasper code and would like a little dir

Re: Jasper DOM API

Hi, I'm also interested in this sort of functionality - I asked a similar question last week. Is it on the roadmap or has any earlier voting process already rejected it as a viable feature? If it hasn't already been rubished as a suggested feature, would I (or Udo) be out of order making an i

Re: jasper questions

Any opinions ? This is a significant change - I won't do it unless I have some feedback. The issues is moving flush() out of PageContextImpl.release() and into the generated java code, just before calling releasePageContext(). My assertion is that release() shouldn't have the flush() as side ef

Re: jasper questions

Remy Maucherat wrote: >> If we let the servlet wrapper deal with it - then we need a 'partial >> flush' >> in release() - which will just move the data to the parent buffer ( >> OutputBuffer from what I see ), but without calling flush on it. >> >> Remy, what do you think ? > > Yes, I think I agr

RE: Jasper 2 Question

Sent: Thursday, September 19, 2002 3:28 PM > To: 'Tomcat Developers List' > Subject: RE: Jasper 2 Question > > > ok .. now I am really confused .. here is the tomcat > development group .. > the 'Official Reference Implementation' for JSP .. and I am &g

Re: Jasper 2 Question

On Friday 20 September 2002 07:27 am, peter lin wrote: > I would also like to see the comments in jasper1 ported over to > jasper2. Now if only I didn't need sleep, I'd do it myself and submit a > patch. the code changed quite a bit between jasper1 and jasper2. the > class responsible is in jaspe

Re: Jasper 2 Question

On Friday 20 September 2002 06:18 am, Pier Fumagalli wrote: > Hm The original question was about line numbers on JSPs, when they > are compiled, and when they are executed and throw exceptions, right? > Yes, it was... > > I said "use some tea" because Tea, developed by Disney, goes exactly in

Re: Jasper 2 Question

I would also like to see the comments in jasper1 ported over to jasper2. Now if only I didn't need sleep, I'd do it myself and submit a patch. the code changed quite a bit between jasper1 and jasper2. the class responsible is in jasper/compiler/Generator in case you get the urge to port the comm

RE: Jasper 2 Question

x27;t buy all the velocity hype... :-) > -Original Message- > From: Lenny Karpel [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 19, 2002 6:28 PM > To: 'Tomcat Developers List' > Subject: RE: Jasper 2 Question > > > ok .. now I am really confus

Re: Jasper 2 Question

On Thursday, September 19, 2002, at 10:24 PM, Bojan Smojver wrote: > On Fri, 2002-09-20 at 04:30, Lenny Karpel wrote: > >> is it right that when I ask a serious question about jasper2 that I >> get >> these totally ridiculous answers ? > > Well, Jon and Pier are known to throw in a curly one fro

Re: Jasper 2 Question

at I get > these totally ridiculous answers ? > > -Original Message- > From: Jon Scott Stevens [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 19, 2002 11:48 AM > To: tomcat-dev > Subject: Re: Jasper 2 Question > > > on 2002/9/19 8:06 AM, "Lenny Kar

RE: Jasper 2 Question

Quoting Lenny Karpel <[EMAIL PROTECTED]>: > this is truly amazing .. how can this possibly be .. My apologies for making you upset :-( It honestly wasn't my intention. Jon helped me with my transition from JSP to Velocity and since then my web apps have become much simpler and easier to maintain

Re: Jasper 2 Question

t; could this possibly be how the 'managers' of this development effort feel > ?? > > -----Original Message- > From: Bojan Smojver [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 19, 2002 3:25 PM > To: Tomcat Dev List > Subject: RE: Jasper 2 Question

RE: Jasper 2 Question

asper) would rather I use something else .. could this possibly be how the 'managers' of this development effort feel ?? -Original Message- From: Bojan Smojver [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 3:25 PM To: Tomcat Dev List Subject: RE: Jasper 2 Question

RE: Jasper 2 Question

On Fri, 2002-09-20 at 04:30, Lenny Karpel wrote: > is it right that when I ask a serious question about jasper2 that I get > these totally ridiculous answers ? Well, Jon and Pier are known to throw in a curly one from time to time, which keeps all of us here on the list in good spirits ;-) Any

RE: Jasper 2 Question

is it right that when I ask a serious question about jasper2 that I get these totally ridiculous answers ? -Original Message- From: Jon Scott Stevens [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 11:48 AM To: tomcat-dev Subject: Re: Jasper 2 Question on 2002/9/19 8:06

RE: Jasper 2 Question

Nooo. No more velocity.. Please.. No more.. > -Original Message- > From: Jon Scott Stevens [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 19, 2002 1:48 PM > To: tomcat-dev > Subject: Re: Jasper 2 Question > > > on 2002/9/19 8:06 AM, "Lenny Karp

Re: Jasper 2 Question

on 2002/9/19 8:06 AM, "Lenny Karpel" <[EMAIL PROTECTED]> wrote: > sorry .. I don't understand your response ! > > are you saying that we shouldn't use jsp ? I have been saying that for years now! http://jakarta.apache.org/velocity/ymtd/ymtd.html =) -jon -- To unsubscribe, e-mail:

RE: Jasper 2 Question

sorry .. I don't understand your response ! are you saying that we shouldn't use jsp ? -Original Message- From: Pier Fumagalli [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 3:57 AM To: Tomcat Developers List Subject: Re: Jasper 2 Question You can use some t

Re: Jasper 2 Question

You can use some tea... http://opensource.go.com/ :-) Pier On Wednesday, September 18, 2002, at 10:33 PM, Lenny Karpel wrote: > I use IntelliJ's IDEA product for Tomcat relared development .. I > noted the > following statement in thier bugs mailing list with regards to > debugging J

RE: Jasper 2 class files

, 2002 8:00 PM To: Tomcat Developers List Subject: RE: Jasper 2 class files However, in the context of JspC, it's a problem to map them to the same package and class name. The custom URLClassLoader works within the JSP engine, but the general servlet class loader doesn't know about those

RE: Jasper 2 class files

files, no matter where they reside, to org.apache.jsp.hello_jsp. > -Original Message- > From: Glenn Nielsen [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, August 21, 2002 7:54 PM > To: Tomcat Developers List > Subject: Re: Jasper 2 class files > > > Yes, you ca

Re: Jasper 2 class files

Yes, you can have two JSP pages with the same name but in different directories and everything will work fine even though they have the same package and class name. This is because a custom URLClassLoader is created for each individual JSP page. That class loader only loads the one java class for

RE: Jasper 2 class files

2 3:16 PM > To: 'Tomcat Developers List' > Subject: RE: Jasper 2 class files > > > If you take the generated class files and war them up and just call them > as servlets how does the classloader differentiate > /org.jasper.jsp.hello_jsp from /subdir/org.jasper.jsp.hello

RE: Jasper 2 class files

o_jsp org.apache.jsp.hello_jsp /subdir/hello.jsp -Original Message- From: Steve Downey [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 21, 2002 2:56 PM To: Tomcat Developers List Subject: Re: Jasper 2 class files Is jspcache the place that Tomcat is lookin

Re: Jasper 2 class files

Is jspcache the place that Tomcat is looking for generated classes? If so, then the custom JSP classloader is doing its magic. The java and class files produced by the JspC command line compiler should be able to be jared up and placed into the WEB-INF directory, like any other servlet. And t

Re: jasper package

> The Java compiler used by Tomcat doesn't have any > problems compiling the > sources that are currently being generated. What > compiler are you trying > to use that has problems with it? That's where your > problem really > appears to lie. > Yes, because the magic class loader has the trick

RE: jasper package

> The compiler driver and classloader used by tomcat > does a lot of magic to > get it to work. All jsp files named, for example, Yes I know the class loader has the job done, is it bearking the convention? Anyway, I can debug my jsp now with the jasper I patched. Yunfeng Hou __

RE: jasper package

ntly, then go ahead and ignore all this. I know this applied for 4.0.3. > -Original Message- > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, August 20, 2002 1:28 AM > To: Tomcat Developers List > Subject: Re: jasper package > > > > > O

RE: jasper package

> -Original Message- > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] > Sent: Monday, August 19, 2002 6:11 PM > To: Tomcat Developers List > Subject: Re: jasper package > > > > > On Mon, 19 Aug 2002, [gb2312] Yunfeng Hou wrote: > > > Date: Mon,

Re: jasper package

On Tue, 20 Aug 2002, [gb2312] Yunfeng Hou wrote: > Date: Tue, 20 Aug 2002 13:13:14 +0800 (CST) > From: "[gb2312] Yunfeng Hou" <[EMAIL PROTECTED]> > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]> > To: Tomcat Developers List <[EMAIL PROTECTED]> >

Re: jasper package

> A desire to do this in the first place probably > comes from wanting to use > unpackaged classes without importing them -- which > is both against the JSP > spec and is also frowned on in general by the Java > compiler in JDK 1.4 and > later. You're MUCH better off putting your classes No, I w

Re: jasper package

On Mon, 19 Aug 2002, [gb2312] Yunfeng Hou wrote: > Date: Mon, 19 Aug 2002 11:35:17 +0800 (CST) > From: "[gb2312] Yunfeng Hou" <[EMAIL PROTECTED]> > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: jasper package > > Jasper has command line option to set pa

Re: [Jasper 2] Tag reuse problems

>>The recent tag reuse changes appear to be great, but seem to have the >>disadvantage of breaking existing tags (for example, the Foo tag in the >>examples, as well as two of the tags from the admin webapp). Although >>none of these tags was compliant with the specification (both had an >>iccorec

Re: [Jasper 2] Tag reuse problems

- Original Message - From: "Remy Maucherat" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Sunday, June 09, 2002 10:42 PM Subject: [Jasper 2] Tag reuse problems > Hi, > > The recent tag reuse changes appear to be great, but seem to have the > disadvantage of

Re: [Jasper 2] Tag reuse problems

I'll test it against my JSTL tag pages and see how it works. peter Remy Maucherat wrote: > > Hi, > > The recent tag reuse changes appear to be great, but seem to have the > disadvantage of breaking existing tags (for example, the Foo tag in the > examples, as well as two of the tags from the

Re: Jasper 2 buggy?

> > --- Additional Comments From [EMAIL PROTECTED] 2002-05-10 22:50 --- > > Jasper 2 is buggy these days after some big refactorings. You can use Jasper 1 > > from other Tomcat releases with Tomcat 4.1, without changing anything else (just > > replace the two Jasper 2 JARs in common/lib w

Re: Jasper error handling extensions

I am in the process of rewriting much of Jasper, and am using an error handling mechanism very similar in idea to the one you just proposed. The new jasper would alos support JSR45, which is an interface for source mapping. The error handler (and other compiler plugins) can be configured with a c

Re: Jasper optimizations

On 29 Aug 2001, Lars Marius Garshol wrote: > | Parsing JSP syntax ( org.apache.jasper34.parser ) will behave as a SAX > | parser, and generate SAX events to generator ( almost identical with what > | XML syntax will generate - the big difference is that we'll generate the > | static content as CD

Re: Jasper optimizations

* [EMAIL PROTECTED] | | Parsing JSP syntax ( org.apache.jasper34.parser ) will behave as a SAX | parser, and generate SAX events to generator ( almost identical with what | XML syntax will generate - the big difference is that we'll generate the | static content as CDATA, instead of parsing it a

Re: Jasper optimizations

On 28 Aug 2001, Lars Marius Garshol wrote: > | I'm working on it - probably next week I'll do another commit with > | the first part of the migration to SAX-based, which is the first > | step to add JSP1.2 features and cleans up even more. > > Does this mean that you intend to completely separate

Re: Jasper optimizations

Hi there, * [EMAIL PROTECTED] | | I'm working on it - probably next week I'll do another commit with | the first part of the migration to SAX-based, which is the first | step to add JSP1.2 features and cleans up even more. Does this mean that you intend to completely separate parsing, tree bui

Re: Jasper optimizations

Hi Lars, > As far as I can tell, the only way to get rid of step #2 is to modify > Jasper. I've looked at the source code, and I think I see a way to do > this with the sources on the MAIN branch. (BTW, is that the latest and > greatest version of Jasper?) The current approach with a tree of > ge

Re: Jasper and parsed tree

Jon Stevens at [EMAIL PROTECTED] wrote: > on 7/13/01 1:49 PM, "Glenn Nielsen" <[EMAIL PROTECTED]> wrote: > >> To me this seems a bit off topic for the list. This list is for Tomcat >> development. Tomcat implements the Servlet and JSP specifications. The >> below has nothing to do with Tomcat

Re: Jasper and parsed tree

on 7/13/01 1:49 PM, "Glenn Nielsen" <[EMAIL PROTECTED]> wrote: > To me this seems a bit off topic for the list. This list is for Tomcat > development. Tomcat implements the Servlet and JSP specifications. The > below has nothing to do with Tomcat development IMHO. > > Regards, > > Glenn Yea

Re: Jasper and parsed tree

To me this seems a bit off topic for the list. This list is for Tomcat development. Tomcat implements the Servlet and JSP specifications. The below has nothing to do with Tomcat development IMHO. Regards, Glenn Brad Cox wrote: > > At 11:40 AM +0800 7/13/01, John Yu wrote: > > >Well, assumi

Re: Jasper and parsed tree

At 11:40 AM +0800 7/13/01, John Yu wrote: > >Well, assuming that the JavaCC grammar is capable of dealing with all >>the intricacies of JSP syntax (and the license issues dealt with), it's >>certainly possible. But I'd be really hesitant to say "let's go replace >>the parser" without discussing

Re: Jasper and parsed tree

> >Well, assuming that the JavaCC grammar is capable of dealing with all >the intricacies of JSP syntax (and the license issues dealt with), it's >certainly possible. But I'd be really hesitant to say "let's go replace >the parser" without discussing and agreeing on an overall architecture >first

Re: Jasper and parsed tree

on 7/11/01 8:19 PM, "John Yu" <[EMAIL PROTECTED]> wrote: > Thanks for the explanation, Craig. > > JCCSP is JavaCC grammar based. (See http://home.earthlink.net/~shemnon/ ) > Would > there be any opportunity to merge this into Jasper? (While it's currently GPL, > Donno has no problem to place it

Re: Jasper and parsed tree

On Thu, 12 Jul 2001, John Yu wrote: > Thanks for the explanation, Craig. > > JCCSP is JavaCC grammar based. (See http://home.earthlink.net/~shemnon/ ) Would > there be any opportunity to merge this into Jasper? (While it's currently GPL, > Donno has no problem to place it under BSD.) > Well,

Re: Jasper and parsed tree

Thanks for the explanation, Craig. JCCSP is JavaCC grammar based. (See http://home.earthlink.net/~shemnon/ ) Would there be any opportunity to merge this into Jasper? (While it's currently GPL, Donno has no problem to place it under BSD.) regards, -- John > > >On Wed, 11 Jul 2001, John Yu wrote

Re: Jasper and parsed tree

On Wed, 11 Jul 2001, John Yu wrote: > I'm new to Tomcat/Jasper. I have a question regarding Jasper: > > Does Jasper parse a JSP into a DOM-like objects. In other words, does Jasper > create in-memory parsed tree of the the JSP file? > It does not currently do this. Essentially, Jasper today

Re: Jasper performance/3.3 tag pooling

>I agree. I spent some time last week looking at possible >optimizations. The general ideas were: > >- pool tag handler objects per application. This could >still be turned on/off at runtime via module and is >already available. > >- cache (re-use) handlers per page - i.e. only get the handler >

Re: Jasper performance/3.3 tag pooling

Hey Mel, I'll use this as a chance to explain some thoughts I've recently had on tag pooling. Maybe you and others have comments. Mel Martinez wrote: > > Hi folks! > > I'm still overwhelmed with other priorities (new job, > house-hunting, moving, etc.) to be able to help again, > but I manag

Re: Jasper performance/3.3 tag pooling

Hi folks! I'm still overwhelmed with other priorities (new job, house-hunting, moving, etc.) to be able to help again, but I managed over the last day or so to get caught up with the list (for the most part - skipped some major threads along the way). On tag-pooling: I am +1 on implementing a t

Re: Jasper performance/3.3 tag pooling

> Thanks for sending the test application. I've been using monthlist.jsp while > testing rendered then hand bashed code. After some preliminary bashing :) > I think it will be possible to call all setters (except runtime expressions) > only once per run of the page. Also, we can create / obtain

Re: Jasper performance/3.3 tag pooling

Rickard, Thanks for sending the test application. I've been using monthlist.jsp while testing rendered then hand bashed code. After some preliminary bashing :) I think it will be possible to call all setters (except runtime expressions) only once per run of the page. Also, we can create / ob

RE: Jasper performance/3.3 tag pooling (XSLT)

Hi Costin, > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, May 23, 2001 10:20 AM > > ... > > I'm working on a refactoring of jasper, and "easy to read" is a big > priority. It's moving a bit slower than I expected - now I'm back on > planning s

Re: Jasper performance/3.3 tag pooling

[EMAIL PROTECTED] wrote: > > Jasper performance is a high priority thing for us (nr 1. on our "system > > performance fixing" list actually), so if possible, absolutely. I can't > > say I've delved that far into Jasper yet though. It was a bit hard to > > read. > > I'm working on a refactoring of

Re: Jasper performance/3.3 tag pooling

I think the changes will be too big to add before the 3.3 freeze. I like your alternative and will start bashing the jsp->java files to get something optimal before changing the jasper34 generator code. I'll let you know when I have something that looks interesting so that it can be discussed b

Re: Jasper performance/3.3 tag pooling

Casey, We hope to freeze 3.3 for a release in the next weeks. If you feel the changes are reasonably small and will not create problems - you can still do it. What about: 1. We copy the code from 3.3 as it is in jasper34 area ( except that we rename the package ). 2. We make sure it builds a

Re: Jasper performance/3.3 tag pooling

Costin & Craig, I agree with both of you. The optimizations that Craig mentioned are exactly the ones that I was hoping to add. Yes, the least fun part will probably be adding to the existing generator code. But, until a new generating architecture is in place, I think it would be good to go

Re: Jasper performance/3.3 tag pooling

On Wed, 23 May 2001, Craig R. McClanahan wrote: > I know Costin loves evolutionary change :-), and it's certainly a valid > approach to Jasper. > > But there is also another approach we should consider - a green-field > recoding of at least some of the major components (conforming to an > agreed

Re: Jasper performance/3.3 tag pooling

On Wed, 23 May 2001 [EMAIL PROTECTED] wrote: > On Wed, 23 May 2001, Casey Lucas wrote: > > > > > btw, If i start tinkering, should I work with jasper34 or the 3.3 stuff? > > Difficult question... > > The problem with jasper34 is that it doesn't work yet ( the one in > proposals/jasper34 - I

Re: Jasper performance/3.3 tag pooling

On Wed, 23 May 2001, Casey Lucas wrote: > > btw, If i start tinkering, should I work with jasper34 or the 3.3 stuff? Difficult question... The problem with jasper34 is that it doesn't work yet ( the one in proposals/jasper34 - I still have to move it in the new repository ). Mea culpa - I trie

Re: Jasper performance/3.3 tag pooling

On Wed, 23 May 2001, Rickard Öberg wrote: > Jasper performance is a high priority thing for us (nr 1. on our "system > performance fixing" list actually), so if possible, absolutely. I can't > say I've delved that far into Jasper yet though. It was a bit hard to > read. I'm working on a refactor

Re: Jasper performance/3.3 tag pooling

Glenn Nielsen wrote: [snip] > > I just had an idea (dangerous things) regarding tag pooling optimizations. > > When Jasper translates a page it should be able to generate information > about which tag handler classes it needs, and for each tag handler, the > profile of the attribute/value pa

Re: Jasper performance/3.3 tag pooling

Glenn Nielsen wrote: > I just had an idea (dangerous things) regarding tag pooling optimizations. > > When Jasper translates a page it should be able to generate information > about which tag handler classes it needs, and for each tag handler, the > profile of the attribute/value pairs. At runti

Re: Jasper performance/3.3 tag pooling

Rickard Öberg wrote: > > [EMAIL PROTECTED] wrote: > > > > We know the pool is synchronized and that may create problems under heavy > > > > load, and we know how to fix this ( by using a per/thread pool without > > > > synchronization ). > > > > > > That is one solution, but what do you do with t

Re: Jasper performance/3.3 tag pooling

[EMAIL PROTECTED] wrote: > But in tomcat 3.3 we do a different trick - the thread pool is maintaining > a "local storage" for each thread, and it's passing it to the worker. > > The only synchronization in tomcat is in getting a thread from the thread > pool - besides that we shouldn't need anyth

Re: Jasper performance/3.3 tag pooling

[EMAIL PROTECTED] wrote: > > > We know the pool is synchronized and that may create problems under heavy > > > load, and we know how to fix this ( by using a per/thread pool without > > > synchronization ). > > > > That is one solution, but what do you do with the pool after page > > request? > >

Re: Jasper performance/3.3 tag pooling

On Tue, 22 May 2001, Rickard Öberg wrote: > > Hash lookup is done once per jsp page - when the jsp page is first run. > > After that, it's basically a synchronized push / pop pair on all subsequent > > runs of the page. In the future we can even get rid of the synch by using > > thread local sto

Re: Jasper performance/3.3 tag pooling

On Tue, 22 May 2001, Rickard Öberg wrote: > Hi! > > [EMAIL PROTECTED] wrote: > > Could you send a small page ( and the taglibs ) and the test conditions ? > > I have sent taglib+page and test conditions to Costin. Thanks, I'll try to add it to the tests dir. > > > We know the pool is synchro

Re: Jasper performance/3.3 tag pooling

Casey Lucas wrote: > Also, did you run the > tests with and without tag pooling enabled on the same version of > tomcat? (By adding removing TagPoolManagerInterceptor.) Yes. The only thing changed between the runs was the TPMI flag. > > This is a bad design. Basically, any gains you get from re

Re: Jasper performance/3.3 tag pooling

Hi! [EMAIL PROTECTED] wrote: > Could you send a small page ( and the taglibs ) and the test conditions ? I have sent taglib+page and test conditions to Costin. > We know the pool is synchronized and that may create problems under heavy > load, and we know how to fix this ( by using a per/thread

Re: Jasper performance/3.3 tag pooling

Rickard, Can you please send in some complete examples? Also, did you run the tests with and without tag pooling enabled on the same version of tomcat? (By adding removing TagPoolManagerInterceptor.) My experience has been that if the jsp uses many tags, then pooling is a big performance gain

Re: Jasper performance/3.3 tag pooling

Hi Rickard, Could you send a small page ( and the taglibs ) and the test conditions ? Most tests I run show a (significant) improvement in performance. We know the pool is synchronized and that may create problems under heavy load, and we know how to fix this ( by using a per/thread pool witho

RE: Jasper performance

> -Original Message- > From: Eduardo Pelegri-Llopart [mailto:[EMAIL PROTECTED]] > Sent: Saturday, May 19, 2001 12:01 AM > > (sorry for the response lag, unfortunatly I don't read tomcat very > frequently) > >... > > * Using XSTL for templating... > > Like Jon and some others, I think th

Re: Jasper performance - JMX

on 5/18/01 10:48 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > On Fri, 18 May 2001, Jon Stevens wrote: > >> Correct, however some bright monkey decided to add <% %> into the JSP >> specification. So, if you disable that, you are breaking the specification. >> In other words, it is a bad d

  1   2   3   >