[OS-webwork] Action reloading
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
[OS-webwork] Improved property tag....
...documentation! I've just checked in new and enhanced documentation for PropertyTag, kindly submitted by Geoff Carruthers (who did put his money where his mouth is, as told, and wrote docs). I'd appreciate it others could have a look and provide feedback, since Geoff has said he's willing to write up more docs to various bits and pieces that are either not documented at all or insufficiently documented. Hani --- 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
Re: [OS-webwork] Improved property tag....
I've just checked in new and enhanced documentation for PropertyTag, kindly submitted by Geoff Carruthers (who did put his money where his mouth is, as told, and wrote docs). I'd appreciate it others could have a look and provide feedback, since Geoff has said he's willing to write up more docs to various bits and pieces that are either not documented at all or insufficiently documented. Ehem, submitted from the wiki (http://www.opensymphony.com:8668/space/The+Three+Uses+Of+The+Property+Tag). So let me get the lifetime of this documentation correct: Geoff wrote The two uses of the property tag, gave it to Mike who posted it on the wiki. I then created The three uses of the property tag that corrected the blatant errors in the first version of the document? I just want credit to be placed where credit is due, because I got the impression from the wiki that Mike wrote the original document that I corrected. (Furthermore I wrote such an incorrect document a long time ago that didn't document the page context use of the property tag, and I submitted it to the list, what ever happened to that?) A very confused box // Anders Hovmöller --- 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
Re: [OS-webwork] Improved property tag....
The docs are NOT original pulled out of thin air type docs. They're just a consolidation of what you, Mike, and various others have written. Feel free to plaster your name and credits wherever you feel is appropriate. In future I'll try to remember to discourage anyone who wants to write docs or do any kind of cleanup effort if it includes a single word uttered by anyone else, to ensure that no copyright infringement takes place. Sorry, didn't know it was that time of month, I was just being curious. // Anders Hovmöller --- 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
Re: [OS-webwork] Improved property tag....
The docs are NOT original pulled out of thin air type docs. They're just a consolidation of what you, Mike, and various others have written. Feel free to plaster your name and credits wherever you feel is appropriate. In future I'll try to remember to discourage anyone who wants to write docs or do any kind of cleanup effort if it includes a single word uttered by anyone else, to ensure that no copyright infringement takes place. On Sunday, November 10, 2002, at 07:09 PM, boxed wrote: I've just checked in new and enhanced documentation for PropertyTag, kindly submitted by Geoff Carruthers (who did put his money where his mouth is, as told, and wrote docs). I'd appreciate it others could have a look and provide feedback, since Geoff has said he's willing to write up more docs to various bits and pieces that are either not documented at all or insufficiently documented. Ehem, submitted from the wiki (http://www.opensymphony.com:8668/space/ The+Three+Uses+Of+The+Property+Tag). So let me get the lifetime of this documentation correct: Geoff wrote The two uses of the property tag, gave it to Mike who posted it on the wiki. I then created The three uses of the property tag that corrected the blatant errors in the first version of the document? I just want credit to be placed where credit is due, because I got the impression from the wiki that Mike wrote the original document that I corrected. (Furthermore I wrote such an incorrect document a long time ago that didn't document the page context use of the property tag, and I submitted it to the list, what ever happened to that?) A very confused box // Anders Hovmöller --- 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 --- 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
Re: [OS-webwork] Improved property tag....
Well, I actually wrote the original two uses of the PropertyTag (which you are correct - is in fact 3, would you believe I didn't know about the third one? ;)) But who writes the docs is fairly irrelevant IMHO - we have better docs for the PropertyTag now *cheer* lets move on and document other things. Cheers, Mike On 11/11/02 11:09 AM, boxed ([EMAIL PROTECTED]) penned the words: I've just checked in new and enhanced documentation for PropertyTag, kindly submitted by Geoff Carruthers (who did put his money where his mouth is, as told, and wrote docs). I'd appreciate it others could have a look and provide feedback, since Geoff has said he's willing to write up more docs to various bits and pieces that are either not documented at all or insufficiently documented. Ehem, submitted from the wiki (http://www.opensymphony.com:8668/space/The+Three+Uses+Of+The+Property+Tag). So let me get the lifetime of this documentation correct: Geoff wrote The two uses of the property tag, gave it to Mike who posted it on the wiki. I then created The three uses of the property tag that corrected the blatant errors in the first version of the document? I just want credit to be placed where credit is due, because I got the impression from the wiki that Mike wrote the original document that I corrected. (Furthermore I wrote such an incorrect document a long time ago that didn't document the page context use of the property tag, and I submitted it to the list, what ever happened to that?) A very confused box // Anders Hovmöller --- 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 --- 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
Re: [OS-webwork] Improved property tag....
And people could add comments I guess. I'm all for it. I'm hanging out for the new version of SnipSnap which should have email notifications - then we can get an email notification of Wiki changes sent to the CVS list? -mike On 11/11/02 12:13 PM, Maurice C. Parker ([EMAIL PROTECTED]) penned the words: On Sunday, November 10, 2002, at 05:50 PM, Hani Suleiman wrote: ...documentation! LOL. What a loaded subject. :-) Hey, I was wondering what you guys thought about moving all the docs into the new Wiki, where it would be easier for people to update. They might stay more current that way. -Maurice --- 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 --- 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
[OS-webwork] Exception handling in BeanUtil
Currently, there are many place in Webwork ( especially BeanUtil ) throw IllegalArgumentException that hide the original exception, this make it much tougher to debug. Any plan improvement/idea for this ? Regards, Low Heng Sin __ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2 --- 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
Re: [OS-webwork] Action reloading
Hani Suleiman wrote: - 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 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. /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
