Nice article, but dangerous and misleading for the following reason: it claims that JOTM is a transaction manager with full distributed transaction support and this is just not true.
A real transaction manager will support crash/restart recovery, and JOTM never did that (did the article mention this somewhere? If so, I must have missed it).
Crashes are a part of life and tend to happen especially on high loads with a maximum number of active transactions. Not having recovery is like smoking a cigarette on a pile of dynamite.
Tricking people into believing that JOTM works correctly can lead to _very_ expensive crashes where data is permanently corrupted. It's like driving a car without brakes: it moves, but as soon as there is an obstacle you crash full speed.
Equally misleading is the article's statement that JOTM can be used to develop robust applications. Not true, especially since it doesn't do recovery.
The law against unfair competition forbids one to make false product claims in most parts of the world. In my opinion, this law has been violated in this article (even if JOTM is open source). The potential damage this article can do to people who believe it is, in my view, enormous.
Also, combining XAPool with MySQL is again dangerous because this combination doesn't support recovery either.
I just wanted to point this out. By the way, I do know what I am talking about since I have designed and developed many JTA transaction managers, all of which support recovery and full distributed transactions.