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 development IMHO. Regards, Glenn Yea, we told him that about a month ago, but it didn't stick. Brad likes to advertise his stuff on other people's lists just so that he can get someone interested in what he is doing. :-( Should I remove him from the bypass moderation pile ??? :) Pier
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 and agreeing on an overall architecture first. I've just uploaded a demonstration of the feasibility of binding web applications to html, template files, properties files, and databases at pre-compile time instead of run-time as most template languages do now. The advantages are considerable; negligible run-time overhead (28kb), compile-time type checking, and so forth. The template language syntax is primitive currently. I'm thinking about modifying the Velocity parser to emit java statements for compilation at compile time instead of interpreting the AST at runtime. Comments on the desirability of this approach are welcome, particularly offers to help! ;) The feasibility demo is at http://virtualschool.edu/jwaa. Tomcat/Velocity developers; I'd be most interested in your responses to my complaints about the emphasis on properties/XML files in Tomcat and Velocity... near the end of the template language document (there's a link to this document at the very top). -- --- For industrial age goods there were checks and credit cards. For everything else there is mybank.dom at http://virtualschool.edu/mybank Brad Cox, PhD; [EMAIL PROTECTED] 703 361 4751
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, 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. I've just uploaded a demonstration of the feasibility of binding web applications to html, template files, properties files, and databases at pre-compile time instead of run-time as most template languages do now. The advantages are considerable; negligible run-time overhead (28kb), compile-time type checking, and so forth. The template language syntax is primitive currently. I'm thinking about modifying the Velocity parser to emit java statements for compilation at compile time instead of interpreting the AST at runtime. Comments on the desirability of this approach are welcome, particularly offers to help! ;) The feasibility demo is at http://virtualschool.edu/jwaa. Tomcat/Velocity developers; I'd be most interested in your responses to my complaints about the emphasis on properties/XML files in Tomcat and Velocity... near the end of the template language document (there's a link to this document at the very top). -- --- For industrial age goods there were checks and credit cards. For everything else there is mybank.dom at http://virtualschool.edu/mybank Brad Cox, PhD; [EMAIL PROTECTED] 703 361 4751 -- -- Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder| MOREnet System Programming | * if iz ina coment. | Missouri Research and Education Network | */ | --
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, we told him that about a month ago, but it didn't stick. Brad likes to advertise his stuff on other people's lists just so that he can get someone interested in what he is doing. :-( -jon
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, 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. regards, -- John Craig
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 under BSD.) regards, -- John Cool! Turn JSP into Velocity (it also uses the JavaCC parser). :-) http://jakarta.apache.org/~jon/jdj_julycover.jpg -jon
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. Understood. I'm wondering what the Jasper's development timetable is. What's the priority to move to a grammar-driven parse? -- John Yu Scioworks Technologies e: [EMAIL PROTECTED]w: +(65) 873 5989 w: http://www.scioworks.com m: +(65) 9782 9610
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 is a bunch of pattern matchers that have associated code generators that are triggered when the patterns are recognized. I notice from Tomcat 4.0's documentation that there's some plan to upgrade Jasper. I'm wondering how that's going and whether the upgrade does anything related to the above area I mentioned. In Tomcat 4.0, the majority of the work was to support the new JSP 1.2 features. The fundamental architecture of Jasper is still pretty much what it was in 3.2. One of the things I'd like to see happen in the 4.x world (and I'm working to acquire some development resources for it) would be a fresh start, looking at JSP page compilation through the eyes of an experienced compiler writer that can leverage all of the tricks optimizing compilers have been using for the last 30 years. There are *lots* of opportunities to generate smaller/faster code, even for the standard JSP 1.2 syntax -- there will be even more opportunities as the JSP Standard Tag Library matures (for example, the page compiler should be able to recognize the JSPTL iteration tag and generate standard Java loop handling code, instead of treating it as a normal custom tag). Thanks in advance. -- John Yu Scioworks Technologies e: [EMAIL PROTECTED]w: +(65) 873 5989 w: http://www.scioworks.com m: +(65) 9782 9610 Craig
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: 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 is a bunch of pattern matchers that have associated code generators that are triggered when the patterns are recognized. I notice from Tomcat 4.0's documentation that there's some plan to upgrade Jasper. I'm wondering how that's going and whether the upgrade does anything related to the above area I mentioned. In Tomcat 4.0, the majority of the work was to support the new JSP 1.2 features. The fundamental architecture of Jasper is still pretty much what it was in 3.2. One of the things I'd like to see happen in the 4.x world (and I'm working to acquire some development resources for it) would be a fresh start, looking at JSP page compilation through the eyes of an experienced compiler writer that can leverage all of the tricks optimizing compilers have been using for the last 30 years. There are *lots* of opportunities to generate smaller/faster code, even for the standard JSP 1.2 syntax -- there will be even more opportunities as the JSP Standard Tag Library matures (for example, the page compiler should be able to recognize the JSPTL iteration tag and generate standard Java loop handling code, instead of treating it as a normal custom tag). -- John Yu Scioworks Technologies e: [EMAIL PROTECTED]w: +(65) 873 5989 w: http://www.scioworks.com m: +(65) 9782 9610
Jasper and parsed tree
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? I notice from Tomcat 4.0's documentation that there's some plan to upgrade Jasper. I'm wondering how that's going and whether the upgrade does anything related to the above area I mentioned. Thanks in advance. -- John Yu Scioworks Technologies e: [EMAIL PROTECTED]w: +(65) 873 5989 w: http://www.scioworks.com m: +(65) 9782 9610
