I know, I know. I plead guilty as charged. :-) Unfortunately, not having a debugger that uses SMP, it is hard to automate SMAP testing. You pretty much has to manually eyeball the files to verify its correctness. I think netbeans is planning to use tomcat 5 for its next major, so we'll expect more use there.
-Kin-man > Date: Tue, 16 Sep 2003 19:46:19 +0200 > From: Remy Maucherat <[EMAIL PROTECTED]> > Subject: Re: cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources messages.properties > To: Tomcat Developers List <[EMAIL PROTECTED]> > > Kin-Man Chung wrote: > > I think keeping an array (in the Template node) of the source line that > > corresponds to each of the Java line we generate is probably enough. I'll > > commit some codes today and you'll see what I mean. > > > > There are reasons for not doing SMAP generation in Generator. Generator is > > already the biggest module in Jasper, and I'd like not to make it any more > > complicated. Also, some codes are generated out of order, in buffers that > > got appended at the end of generating the main method, so that the mappings > > cannot be determined when codes are generated. > > > > SMAP generation is one of the area that does not got enough test and use. > > You seem to be one of the few who actually look at it. Are you doing anything > > with it? > > Given the number of bug reports which have been filed against that > single feature, I can assert this is not the case. You should rewrite > your sentence as "SMAP generation is one of the area that does not get > enough test and use among Tomcat committers" ;-) > > Remy > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
