DO NOT REPLY [Bug 20516] - Jasper2 compilation not JSP 2.0 compliant on J2SE 1.4
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20516. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20516 Jasper2 compilation not JSP 2.0 compliant on J2SE 1.4 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-06-09 18:40 --- I've marked this bug that I submitted as invalid because I'm retracting it completely. For the record, Jasper2 fully supports JSR-045 on J2SE 1.4 and the SourceDebugExtension attribute from the class file that Jasper generates contains a fully conformant SMAP. This bug was submitted in error due to a misunderstanding between myself and my development team on how WebLogic JSP debugging was being supported and the differences with the Tomcat 5 implementation. As a result of this misunderstanding, I posted this bug in error. I'm sorry for any inconveniences that this may have caused to anyone. Simply FYI for the interested, the next release of MyEclipse Enterprise Workbench (www.myeclipseide.com), which is scheduled for release on 6/16/2003, will contain full source level JSP debugging support for Tomcat 5 using its JSR- 045 implementation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20516] - Jasper2 compilation not JSP 2.0 compliant on J2SE 1.4
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20516. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20516 Jasper2 compilation not JSP 2.0 compliant on J2SE 1.4 --- Additional Comments From [EMAIL PROTECTED] 2003-06-05 20:31 --- As far as jasper is concern, it is responsible for generating the smap in the SourceDebugExtension attribute of the class file. How other tools uses this information is not its concern. I have dumped the generated class file, and as far as I can tell, the SourceDebugExtension attribute contains the correct information. If you can point out the problems here, I'll fix them. Perhaps if you compare the class files generated by Jasper to those generated by Weblogic, you'll be able to tell me what Jasper is doing wrong. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20516] - Jasper2 compilation not JSP 2.0 compliant on J2SE 1.4
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20516. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20516 Jasper2 compilation not JSP 2.0 compliant on J2SE 1.4 --- Additional Comments From [EMAIL PROTECTED] 2003-06-05 20:55 --- Kin-Man, Thank you for looking into the generation within Jasper 2. I'll do exactly as you suggested and compare the WebLogic output with Jasper 2 and post my findings back here once I've completed the analysis. It could be that Jasper 2 is correct and WebLogic is wrong. Todd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
