LIXA (LIbre XA) is an open source and free Transaction Manager implementing the distributed transaction processing "XA specification" and "TX (transaction demarcation) specification" according to the X/Open CAE Specification. LIXA is a Transaction Manager but it's not a Transaction Monitor: this is the distinguishing feature of the project.
LIXA technology enables every application container, like a web server or a shell, to become an XA compliant application server. The client/server architecture of LIXA allows many application containers to share a single LIXA (state) server: this is ideal when horizontal scalability is a must and many identical application containers must refer to a single transactional environment. Performance, scalability and high availability are key features of the project.
The source code provided by the LIXA project can be considered quite stable and the usage in non trivial environment should be feasible.
The questions before further development are many:
A different evolution path could be the implementation of a native Java version supporting the JTA standard: implementing a native Java LIXA client able to connect to the standard LIXA state server could exploit a highly horizontal scalable transaction manager indipendent from any JEE application server. The final result could be something like BTM (Bitronix Transaction Manager) with native horizontal scalability.
The question is: "is there any room for another transaction manager not embedded in an application server"?
Creating an API for interpreted languages like PHP was already done but the PHP community expressed no interest related to "two phase commit" and "distributed transaction processing".
Your feedback is precious: don't esitate to post your ideas using the LIXA mailing list.