So, there are three different flavors? Why "ERX" and "ERXWO" and "Ajax" of the same thing?
Perhaps it is just a general rule for understanding Wonder: There are at least three ways of doing anything: ak-ish, ms-ish, and ch-ish. :-)
It kind of makes as much sense as any other explanation....
Another explanation might be that they do different things and meet the needs of different requirements?
AjaxLongResponse: uses an Ajax periodic update to refresh its component content as long as the isRunning binding returns true
* ERXLongResponse is like WOLongResponsePage from JavaWOExtensions, but
* it can be used as a component and doesn't need to be subclassed.
* Instead, you provide a ERXLongResponseTask subclass and set it
* via either the bindings or explicitely.
ERXWOLongResponsePage: javadoc says it better than i can
* ERXWOLongResponsePage is just like WOLongResponsePage except that it
* cleans up editing context locks at the end of run() just like the behavior
* at the end of a normal R-R loop.
WOLongResponsePage: this is the original -- all of JavaWOExtensions was brought into Wonder
so, WOLongResponsePage is just the bare-slate original
ERXWOLongResponsePage (which probably could be autopatched in, actually) is what you would use if you want autolocking in your long response.
ERXLongResponse is what you would use if you want to use a task object and that pattern instead of subclassing in the traditional way
AjaxLongResponse is just an Ajax refreshing wrapper around a component content, but might fit better in an environment that is already doing Ajax-y things.