Hani Suleiman wrote:
Since we're all using Ant (right?), isn't it better to have some standard action that does the reloading. Then one can let the Ant script hit that action explicitly after compiling in order to reload. This would remove the overhead for watching files.- It ONLY reloads actions. It specifically does not reload any classes outside of the defined packages for actions. - It relies on the location of webwork.properties to determine what the jar/directory where actions exist - No extra configuration is required beyond changing the action factory in default.properties to use ReloadingActionFactory - Usual performance overhead of monitoring files for change - No recompiling of source files is done, you'd still have to use ant/whatever to compile your class and have it end up in the right place (where the appserver expects it, basically) - If an appserver monitors every class in the webapp and reloads on any change, then this factory is useless - Only tested on orion
/Rickard
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
