[OS-webwork] Action reloading

[Hani Suleiman]

I've written a custom ActionFactory which reloads action dynamically. In effect, this means you can change the code for your actions, compile, and hit refresh and see the changes. I'd like to know if there's any interest in adding this to core webwork, knowing that it has a number of features/limitations:

- 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

The benefit for me has mainly been in that I do not need to go through a restart or still very relatively slow webapp redeployment for just having added an accessor to my action.



-------------------------------------------------------
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