This is great and is sorely needed. I am all for it! It'd be nice if the new API also include supports for JSR-45 (Debugging Support for Other Languages). For instance, when invoking javac with a smap file, javac should
1) report errors by JSP page source and line numbers, and 2) incoporate the informantion in the smap file into the resultant class file. Step 1) would eliminate an ugly part of Jasper, which parses javac errors messages for the line number in the generated java files to report errors in the orginal JSP file. Step 2) would eliminate a post (javac) processor to do the same. If these are not feasible, then at least include in the API a way to inform the client of the error locations programmatically. Thanks. > Date: Thu, 10 Oct 2002 16:39:29 -0700 > From: Neal M Gafter <[EMAIL PROTECTED]> > Subject: New JSR on Java(TM) Compiler API > To: [EMAIL PROTECTED] > > [I am resending this due the Mozilla's munging of the attachment on the previous try] > > Tomcat developers- > > I am starting up a new JSR on an API for invoking a Java Language compiler from within > a Java program. A draft of the JSR proposal is enclosed. This API would be very useful > anywhere a Java program will want to invoke the Java Compiler, for example ANT rebuilds, > Java Server Pages, or anywhere an application wants to turn a small snippet of Java code > into a Class efficiently. In addition, this API calls for the compiler to provide > dependency information after compiling, which would help support incremental rebuilds. > > I am in the process of gathering support for this JSR to help it along the initial stages > of the Java Community Process. Your comments are most welcome. > > Regards, > Neal Gafter > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
