Guy, thank you for your feedback on this article and JOTM.
I clearly stated that JOTM helps to create more robust web applications. It was never my intent to write that JOTM makes your web applications ultimately robust. I still believe that even without recovery, JOTM makes web applications more robust and simple. But it's true that there is much more to have robust web applications.
Concerning recovery, JOTM team has never hidden the fact that it does not support recovery.
In the context of this article, we introduced JOTM and focused on its features. Perhaps, I should have added a section on the current limitations of JOTM (guess what? it's not bug free! ;-).
You're well aware that there isn't any Java Open Source Transaction manager which provides recovery. But, nevertheless, JOTM is pushing very hard to be the first to implement it. It has a unique opportunity to do so.
Indeed, JOTM has been relicensed to become the defaut transaction manager of both ObjectWeb/JOnAS and Apache/Geronimo.
The two communities have decide to join their effort and to contribute to JOTM and to its recovery subprojects (HOWL). So, we acknowledged we lack recovery but we're making big commitments to meet that need.
I think you're unfair when you suggest that I deliberately lied in this article to trick people. You've followed the JOTM project for long enough to know that we don't cheat our users. We believe in Open Source, we're objective
about our product and our concurrence (including your own product).
However, I took into account your critics and I'd like to write a followup to this article when recovery is implemented in JOTM showing how it helps creating even more robust web applications.