I can't see how we can get java compilers to use our classloaders without actually modifying the javac compilers. Ant does not do this - it passed a classpath that you have specified in the build.xml
The fundamental problem is that JSPs are not well designed when it comes to deployment, as you essentially need to support a miniture IDE on an arbitrary platform. IMHO it is outside the scope of Jetty and/or JBoss to try to solve the design problems of JSPs I think that the best that we can do is to make a best effort approach to determine a file classpath that we can pass to the JspServlet. We should also provide good override mechanisms to allow a deployer (or ear developer) to explicitly set the classpath passed to the JspServlet Of course this is only a half arsed solution - but then I think JSPs are the thing that is half arsed. If you think about it, the chances of any compiler following the inverted classloading priorities of the latest servlet spec are zero anyway. So the runtime classpath will load jars from the context in preference to the compilers ext directory, but at compile time, you will almost certainly get the jars from the ext directory. To try specifying the boot classpath would just be way to platform dependant. So I think that anybody with a non trivial context classpath is going to have all sorts of JSP compile problems anyway. So I think we should stop trying to solve JSPs problems - take a best guess at a file classpath and then suggest pre-compilation if they get any deployment problems. cheers marc fleury wrote: > |Yeap, jikes is not java -- it is C++. Also, it may very well be so that > |even Sun's compiler can't do this. In Tomcat they configure a command line > |for sun.tools.javac which has a special -classpath switch. Don't know if > |the jvm uses it or javac itself reads the entries in the classpath and > |loads classes from there bypassing CL mechanisms. > | > |This sucks big time, because if you don't precompile JSPs, you end up > |having to trag all the necessary .class files into the WAR. No > |integration... > > well then FUCK it ! > > we use the invm javac, we tweak it to be in process with the right CL and > VOILA! > > If ANT can do it we can do it, and don't give me the "speed" booboo, the > speed of javac in process is diabolical. It takes what 20 seconds to > compile the WHOLE of JBOSS? so your 2-3 little JSP are not going to impress > Javac invm > > marcf > > | > | > |> > |> -dain > |> > |> _______________________________________________ > |> Jboss-development mailing list > |> [EMAIL PROTECTED] > |> https://lists.sourceforge.net/lists/listinfo/jboss-development > |> > | > -- Greg Wilkins<[EMAIL PROTECTED]> GB Phone: +44-(0)7092063462 Mort Bay Consulting Australia and UK. Mbl Phone: +61-(0)4 17786631 http://www.mortbay.com AU Phone: +61-(0)2 98107029 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
