DO NOT REPLY [Bug 6908] - JavaCompiler interface setOutputDir always called with null parameter
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=6908. 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=6908 JavaCompiler interface setOutputDir always called with null parameter [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2002-04-22 20:50 --- When I executed the test page index.jsp, and got the expected reponse The lines below are just some jsp code to make sure this page compiles 1 and DummyCompiler is never executed. setOutputDir has been working correctly, for both SunJavaCompiler and JikesJavaCompiler, and if it doesn't work for you, you'll just need to debug your code. Sorry. If you can find places in the source that's wrong, please submit a patch, but I examined the code again and couldn't find anything that's obviously wrong. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6908] - JavaCompiler interface setOutputDir always called with null parameter
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=6908. 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=6908 JavaCompiler interface setOutputDir always called with null parameter --- Additional Comments From [EMAIL PROTECTED] 2002-04-02 10:13 --- Created an attachment (id=1462) compiler wrapper test-app -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6908] - JavaCompiler interface setOutputDir always called with null parameter
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=6908. 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=6908 JavaCompiler interface setOutputDir always called with null parameter [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2002-04-02 10:16 --- I have retested this bug and I am still seeing calls to setOutputDir with a null parameter. I have attached a simple web-app that demonstrates the problem. It wraps the SunJaveCompiler Class in the DummyCompiler (in WEB-INF\src\nl\secorp\jsp\compiler\DummyCompiler.java) The following is printed to stdout if http://localhost:8080/compiler- test/index.jsp is requested: == START STDOUT === setEncoding(UTF8) setClasspath(c:\program files\java\j2re1.4.0\lib\rt.jar;c:\jakarta-tomcat-4.0 \bin\bootstrap.jar;C:/jakarta-tomcat-4.0/webapps/compiler-test/WEB- INF/classes;C:/jakarta-tomcat-4.0/webapps/compiler-test/WEB- INF/classes;C:/jakarta-tomcat-4.0/classes/;C:/jakarta-tomcat-4.0/lib/jasper- compiler.jar;C:/jakarta-tomcat-4.0/lib/jasper-runtime.jar;C:/jakarta-tomcat- 4.0/lib/naming-factory.jar;C:/jakarta-tomcat- 4.0/lib/nl.secorp.guid.jar;C:/jakarta-tomcat- 4.0/lib/nl.secorp.jsp.jar;C:/jakarta-tomcat- 4.0/lib/org.eclipse.java.compiler.jar;C:/jakarta-tomcat- 4.0/common/classes/;C:/jakarta-tomcat-4.0/common/lib/mm.mysql-2.0.11- bin.jar;C:/jakarta-tomcat-4.0/common/lib/naming-common.jar;C:/jakarta-tomcat- 4.0/common/lib/naming-resources.jar;C:/jakarta-tomcat- 4.0/common/lib/servlet.jar;C:/jakarta-tomcat-4.0/common/lib/tools.jar) setOutputDir(null) setMsgOutput() setClassDebugInfo(false) compile(C:\jakarta-tomcat-4.0\work\localhost\compiler-test\\index$jsp.java) == END STDOUT === -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6908] - JavaCompiler interface setOutputDir always called with null parameter
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=6908. 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=6908 JavaCompiler interface setOutputDir always called with null parameter --- Additional Comments From [EMAIL PROTECTED] 2002-04-02 10:31 --- I have a feeling that the command line jsp compiler works OK since it uses CommandLineContext CommandLineContext.getJavacOutputDir returns scratchdir JspEngineContext.getJavacOutputDir returns null! -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6908] - JavaCompiler interface setOutputDir always called with null parameter
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=6908. 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=6908 JavaCompiler interface setOutputDir always called with null parameter [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-03-30 00:08 --- That is not the expected behavior, and should not happen. How did you arrive at the conclusion that JavaCompiler.setOutputDir is called with only null parameter? It wouldn't have worked for even the simplest jsp page if it were so. If you care to search the sources for setOutputDir, you'll see that it is called in compiler/Compiler.java, and the logic that computes the outdir is in servlet/JspServlet.java. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
