Hi,
Again, why not simply remove the requirement that development=false?
There is nothing stopping you from recompiling JSP files explicitly with
this configuration, right?
The production application will not accept it.
Why the second request? The compile/load step should be all handled in a
single request!
The second request is used to execute JSP page.
Where is the "class" (in a file? where?) and how are you trying to load it?
The class file is placed at
$CATALINA_HOME/work/localhost/_/org/apache/jsp/test/_1_jsp.class.
I'm sorry, my brain can't make any sense out of that "sentence".
The first request has loaded it ,if my compiler set precompile=false, it will
execute that page well,but if precompile=true,and the class loader can't found
it in next request.
Wait, you're recompiling ClassLoaders on the fly, now, too?None of this makes
any sense. You are completely wasting your time
trying to do something that is completely unnecessary.
You can image that there are 10000 pages,99.9% of them do not need to
recompile, but a little needs to do,that's way the development parameter
unnecessaryly set true.
I has implemented this requirement,but still do not know the reason why the
whole operation can't be separated.
Thank you for your time. :-)
Kind regards,
Mercy
Christopher Schultz 写道:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mercy,
On 10/9/2009 10:06 PM, Mercy wrote:
My JSP compiler is based on JspServletWrapper(Jasper compiler).
Again, why not simply remove the requirement that development=false?
There is nothing stopping you from recompiling JSP files explicitly with
this configuration, right?
My JSP compiler use JspServletWrapper ,thus, it will compile and
load(ClassLoader works fine) once,
Sounds good.
here is recompiled operation,and then a new request (by JspServlet) to
load that compiled JSP,
Why the second request? The compile/load step should be all handled in a
single request!
the ClassLoader can't find class.
Where is the "class" (in a file? where?) and how are you trying to load it?
ClassLoader loadClass method can find
the class that it loaded before
Okay, then where is /that/ class? Are you simply not writing the .class
file into the right place?
, thus I think JapserLoader should load
that class,but it can't find.
I'm sorry, my brain can't make any sense out of that "sentence".
Should it pass the recompiled ClassLoader to loader ClassLoader as
parent ClassLoader? :-)
Wait, you're recompiling ClassLoaders on the fly, now, too?
None of this makes any sense. You are completely wasting your time
trying to do something that is completely unnecessary.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkrQhvkACgkQ9CaO5/Lv0PAYWACgoxdbR+iYYUOurB5tH+POjGPm
X0UAoKh9Ff90LuQa9APeXdN5KXhniTwJ
=unUf
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
