Upayavira wrote:
Wow. You really must not reload the cocoon servlet at each request. The servlet does a lot of things like initialising loads of avalon objects, etc. If you did that at every request, you can expect your servlet container to die very quickly.
Jetty can reload a class if you compile it while at a breakpoint, I use that regularly. But to have it reload when a class has changed would be really neat.
Regards, Upayavira
Dear Upayavira,
I modified the "JavaInterpreter.java" file in order for Cocoon to reload a .class file
when it detects a modification in time. Please, read the following instructions, in case
you want to try it
1. Before running Cocoon, you need to set the environment variable COCOON_HOME
to the absolute path of your installation. I'm using a batch file with the following
content:
set COCOON_HOME="D:\Programmi\cocoon\cocoon-2.1.53"
cocoon servletCocoon, on my PC, is indeed installed in "D:\Programmi\cocoon\cocoon-2.1.53"
2. I posted the modified: "JavaInterpreter.java" and "cocoon-javaflow-block.jar"
files at the following URL
http://www.foskeea.org/cocoon/javaflow-modified.zip
3. The modifications I made are meant for debug purposes only. Because, as you
know, the current release of Cocoon (2.1.5) doesn't reload .class files.
I used the "File.separator" field in order for the modifications to run on any
platform.
4. Each time you modify a .class file, please have your URL point to the initial URI
of your web application, to start fresh a new debug session.
I'm using it and hope it'll help others,
ciao Enrico
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
