I'm not a tomcat dev, but hopefully I can help anyway - having done what I think it is you're trying to do. I did mine for the Winstone servlet container (http://winstone.sourceforge.net)
For Nos 1 and 2, I can't help. But for No 3 it involves setting context attributes:
1) org.apache.catalina.jsp_classpath, and
2) org.apache.catalina.classloader
It seems that 1 is the one that does the work. It doesn't actually even seem to call 2 at class load time, but there is code that reads 2, so I set it anyway.
By setting 1, you don't actually set the classloader, but you make a new classloader that has the same classpath. If that's not what you want, maybe someone else on the list can help.
The only other thing you have to do is mount the JspServlet, which it sounds like you've already done.
R
Dennis Thrysøe wrote:
Hi,
I'm currently working on embedding a jasper engine within a servlet container that I'm writing. During this work I have run into the following questions:
1) Is the only advantage to using fork=true, that the javac memory leak issue is avoided?
2) Has the javac memory leak issue been fixed in newer versions of the JDK?
3) Is there any way to have the Java code generated from JSPs compiled using my own classloader? I was thinking, that if I used fork=false, maybe javac would just use the present classloader.
Any help with the above questions would be greatly appreciated, since it seems that I'm on a fairly difficult endeavour here.
TIA,
-dennis
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
