Re: JSR 199 (Jsr199JavaCompiler) compile errors
Mark, Thank you for your reply. I am aware that Glassfish is not Tomcat. However, it seems to me that since the class in question is managed by Apache that there must have been some level of collaboration between the two teams and a reasonable assumption on my part that Apache may have been working to enable Jasper to address JSR 199. It appears that you are implying something to the contrary; along the lines that Sun may have taken a snapshot of Jasper and modified it specifically for Glassfish perhaps. This is certainly possible but, I don't see this as feasible since they have made the statement that they (Sun) have adopted Jasper as their compiler. With all that said, it still leaves me in a place where I'm wondering how Jasper might be used to actually compile a JSP outside of using the ANT or JSPC approach. Now, that Java SE 6 has a nice Compile class it seems like we are much closer to being able to take a standardized approach to real-time compilation. This, in essence is what I am attempting to explore. The class I mentioned appeared, at least on the surface, to be such an effort on the part of Sun and Apache. I am willing to concede that perhaps it is not and would like that clarification from Apache or Sun should that be the case. Thanks, Fran Mark Thomas-15 wrote: Fran Varin wrote: Thank you for your reply. I d/l'd from the following location: http://repo1.maven.org/maven-java.net/jasper-jsr199/java-sources/ The information was based on this article: http://blogs.sun.com/kchung/entry/speed_up_jsp_compilations_with Glassfish != Tomcat There is no guarantee that the internal interfaces are the same. Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JSR-199-%28Jsr199JavaCompiler%29-compile-errors-tf4629050.html#a13231996 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSR 199 (Jsr199JavaCompiler) compile errors
Mark, I did some further digging and d/l'd the source for Glassfish. I have found that Glassfish indeed does include a version of Jasper that appears to have been modified. This confirms some of my thinking in my previous response. However, it does leave me with an uncomfortable feeling. I'm not comfortable with a statement that indicates Glassfish uses Jasper as the compiler when it is not an off the shelf version. It means to me, as a developer, that the advancements that are made appear to have not been contributed back, or at least made there way back, into the mainstream code base; in this case Jasper. So, to take advantage of this, I would need to fork the Sun version even further to try and remove any specifics that Sun may have added solely for their purpose. So, I guess the question is, does Apache intend on rolling the JSR 199 functionality into Jasper? Or is there an alternative that Apache has to offer or is possibly working on? Thanks, Fran Fran Varin wrote: Mark, Thank you for your reply. I am aware that Glassfish is not Tomcat. However, it seems to me that since the class in question is managed by Apache that there must have been some level of collaboration between the two teams and a reasonable assumption on my part that Apache may have been working to enable Jasper to address JSR 199. It appears that you are implying something to the contrary; along the lines that Sun may have taken a snapshot of Jasper and modified it specifically for Glassfish perhaps. This is certainly possible but, I don't see this as feasible since they have made the statement that they (Sun) have adopted Jasper as their compiler. With all that said, it still leaves me in a place where I'm wondering how Jasper might be used to actually compile a JSP outside of using the ANT or JSPC approach. Now, that Java SE 6 has a nice Compile class it seems like we are much closer to being able to take a standardized approach to real-time compilation. This, in essence is what I am attempting to explore. The class I mentioned appeared, at least on the surface, to be such an effort on the part of Sun and Apache. I am willing to concede that perhaps it is not and would like that clarification from Apache or Sun should that be the case. Thanks, Fran Mark Thomas-15 wrote: Fran Varin wrote: Thank you for your reply. I d/l'd from the following location: http://repo1.maven.org/maven-java.net/jasper-jsr199/java-sources/ The information was based on this article: http://blogs.sun.com/kchung/entry/speed_up_jsp_compilations_with Glassfish != Tomcat There is no guarantee that the internal interfaces are the same. Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JSR-199-%28Jsr199JavaCompiler%29-compile-errors-tf4629050.html#a13233145 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSR 199 (Jsr199JavaCompiler) compile errors
Fran Varin wrote: Mark, Thank you for your reply. I am aware that Glassfish is not Tomcat. However, it seems to me that since the class in question is managed by Apache that there must have been some level of collaboration between the two teams Tomcat was originated with a code donation from Sun. Some time ago (I forget exactly when), Sun started Glassfish and forked the Tomcat code as a starting point. and a reasonable assumption on my part that Apache may have been working to enable Jasper to address JSR 199. I am not aware of any efforts in this direction. It appears that you are implying something to the contrary; along the lines that Sun may have taken a snapshot of Jasper and modified it specifically for Glassfish perhaps. Exactly. This is certainly possible but, I don't see this as feasible since they have made the statement that they (Sun) have adopted Jasper as their compiler. I haven't seen that statement so can't comment. With all that said, it still leaves me in a place where I'm wondering how Jasper might be used to actually compile a JSP outside of using the ANT or JSPC approach. Now, that Java SE 6 has a nice Compile class it seems like we are much closer to being able to take a standardized approach to real-time compilation. This, in essence is what I am attempting to explore. Patches are always welcome. The class I mentioned appeared, at least on the surface, to be such an effort on the part of Sun and Apache. I am willing to concede that perhaps it is not and would like that clarification from Apache or Sun should that be the case. The above should clarify this. HTH, Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSR 199 (Jsr199JavaCompiler) compile errors
Mark, Thank you for your note, it does clear up the confusion over this quite a bit. Regarding your comment that patches are always welcome. I am interested in pursuing this with the Jasper code base. What channels do I need to go through to open up a clear line of communication/assistance with this? I'm willing to put some of my time in on it but, would like the reassurance that I can gain access to the Jasper developers to work with them. Fran Mark Thomas-15 wrote: Fran Varin wrote: Mark, Thank you for your reply. I am aware that Glassfish is not Tomcat. However, it seems to me that since the class in question is managed by Apache that there must have been some level of collaboration between the two teams Tomcat was originated with a code donation from Sun. Some time ago (I forget exactly when), Sun started Glassfish and forked the Tomcat code as a starting point. and a reasonable assumption on my part that Apache may have been working to enable Jasper to address JSR 199. I am not aware of any efforts in this direction. It appears that you are implying something to the contrary; along the lines that Sun may have taken a snapshot of Jasper and modified it specifically for Glassfish perhaps. Exactly. This is certainly possible but, I don't see this as feasible since they have made the statement that they (Sun) have adopted Jasper as their compiler. I haven't seen that statement so can't comment. With all that said, it still leaves me in a place where I'm wondering how Jasper might be used to actually compile a JSP outside of using the ANT or JSPC approach. Now, that Java SE 6 has a nice Compile class it seems like we are much closer to being able to take a standardized approach to real-time compilation. This, in essence is what I am attempting to explore. Patches are always welcome. The class I mentioned appeared, at least on the surface, to be such an effort on the part of Sun and Apache. I am willing to concede that perhaps it is not and would like that clarification from Apache or Sun should that be the case. The above should clarify this. HTH, Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JSR-199-%28Jsr199JavaCompiler%29-compile-errors-tf4629050.html#a13233927 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSR 199 (Jsr199JavaCompiler) compile errors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fran, Fran Varin wrote: What channels do I need to go through to open up a clear line of communication/assistance with this? Report a bug/enhancement. Post a patch. You'll get a response: believe me. I'm willing to put some of my time in on it but, would like the reassurance that I can gain access to the Jasper developers to work with them. Most if not all of the Tomcat devs lurk on this list (including Mark, Bill, Tim, Filip, Rainer, Remy, and Mladen -- I assume others are here but less vocal). Your contributions will not go ignored. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHFOLS9CaO5/Lv0PARAjR6AJ9jUHW6h3I19Gs6PiZ6jMNHr5KLXwCdFqIt qZNcPqMmkWhvNDjDpBeTifY= =C2yc -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JSR 199 (Jsr199JavaCompiler) compile errors
I have a question regarding JSR 199 bridge (class Jsr199JavaCompiler). I have downloaded the most recent version of the source however there appears to be an inconsistency with the version of the classes “JspCompilationContext” and “JspRuntimeContext” that it expects to use. The following methods are reported as undefined: saveBytecode(line 118 in “saveClassFile”) getFullClassName (line 156 in “getClassLastModified”) getBytecodeBirthTime (line 157 in “getBytecodeBirthTime”) setBytecode (line 206 in “compile”) getPackageMap (line 266 in “getOutputFile” and line 328 in “getJavaFileManager”) I see no reference or mention of version dependency in the “jsr199JavaCompiler”? What am I missing? -- View this message in context: http://www.nabble.com/JSR-199-%28Jsr199JavaCompiler%29-compile-errors-tf4629050.html#a13217711 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSR 199 (Jsr199JavaCompiler) compile errors
where did you d/l the package? M-- - Original Message - From: Fran Varin [EMAIL PROTECTED] To: users@tomcat.apache.org Sent: Monday, October 15, 2007 1:29 PM Subject: JSR 199 (Jsr199JavaCompiler) compile errors I have a question regarding JSR 199 bridge (class Jsr199JavaCompiler). I have downloaded the most recent version of the source however there appears to be an inconsistency with the version of the classes “JspCompilationContext” and “JspRuntimeContext” that it expects to use. The following methods are reported as undefined: saveBytecode(line 118 in “saveClassFile”) getFullClassName (line 156 in “getClassLastModified”) getBytecodeBirthTime (line 157 in “getBytecodeBirthTime”) setBytecode (line 206 in “compile”) getPackageMap (line 266 in “getOutputFile” and line 328 in “getJavaFileManager”) I see no reference or mention of version dependency in the “jsr199JavaCompiler”? What am I missing? -- View this message in context: http://www.nabble.com/JSR-199-%28Jsr199JavaCompiler%29-compile-errors-tf4629 050.html#a13217711 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSR 199 (Jsr199JavaCompiler) compile errors
Thank you for your reply. I d/l'd from the following location: http://repo1.maven.org/maven-java.net/jasper-jsr199/java-sources/ The information was based on this article: http://blogs.sun.com/kchung/entry/speed_up_jsp_compilations_with I have also taken a look at the source for recent versions of Jasper and have not been able to match up the method names mentioned that are flagged in error. This leads me to believe that I'm missing something here. Thanks for your time, Fran mgainty wrote: where did you d/l the package? M-- - Original Message - From: Fran Varin [EMAIL PROTECTED] To: users@tomcat.apache.org Sent: Monday, October 15, 2007 1:29 PM Subject: JSR 199 (Jsr199JavaCompiler) compile errors I have a question regarding JSR 199 bridge (class Jsr199JavaCompiler). I have downloaded the most recent version of the source however there appears to be an inconsistency with the version of the classes “JspCompilationContext” and “JspRuntimeContext” that it expects to use. The following methods are reported as undefined: saveBytecode(line 118 in “saveClassFile”) getFullClassName (line 156 in “getClassLastModified”) getBytecodeBirthTime (line 157 in “getBytecodeBirthTime”) setBytecode (line 206 in “compile”) getPackageMap (line 266 in “getOutputFile” and line 328 in “getJavaFileManager”) I see no reference or mention of version dependency in the “jsr199JavaCompiler”? What am I missing? -- View this message in context: http://www.nabble.com/JSR-199-%28Jsr199JavaCompiler%29-compile-errors-tf4629 050.html#a13217711 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JSR-199-%28Jsr199JavaCompiler%29-compile-errors-tf4629050.html#a13219037 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSR 199 (Jsr199JavaCompiler) compile errors
Fran Varin wrote: Thank you for your reply. I d/l'd from the following location: http://repo1.maven.org/maven-java.net/jasper-jsr199/java-sources/ The information was based on this article: http://blogs.sun.com/kchung/entry/speed_up_jsp_compilations_with Glassfish != Tomcat There is no guarantee that the internal interfaces are the same. Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
