Secondly, reloading the entire webapp can be quite slow if you have complex init on startup servlets. My 'hack' would just reload all actions, rather than the entire webapp.
On Nov 6, 2003, at 3:49 AM, Dick Zetterberg wrote:
What does the reloading mean really? That you can compile an action and Webwork will notice that it changed and update the class?
How is this different from what the container would do if I tell it to detect changes to my classes? That it only reloads the changed class?
Cheers,
Dick Zetterberg [EMAIL PROTECTED]
----- Original Message ----- From: "Hani Suleiman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 05, 2003 6:16 AM Subject: [OS-webwork] action reloading
Is there any interest (or objections) regarding moving action class
reloading into ww1.3 core? I've had a couple of requests for that. It
is currently an extra jar that duplicates a lot of what is available in
core, so moving it in would basically involve checking in a classloader
and a couple of statements inside of core, as well as docs warning
people against using it in a production environment ;)
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
