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]
