Hi guys, if you watched meecrowave commits, you probably saw i pushed a JTA module.
Here few comments about it cause it can be surprising in meecrowave context: - first point is JTA is still needed sometimes and microservices or not you can need to connect multiple instances somehow. Not the best perf you'll get but the best consistency - trade off ;). This is typically the case for JMS/Database integrations which are not uncommon in microservices (don't ask me why) - all the work done around JPA and now JTA is to make anything CDI beans, ie the TransactionManager being a CDI bean (either a default or user provided one) and not a resource you need to customize in a limited manner in the server or through a very specific SPI: here the SPI is the IoC/CDI I don't plan to add a tons of EE backports but thought it was important to explain why it was done there and not directly at geronimo or another project. The last point being not natural for EE makes meecrowave a good home for it, trying to propose a more natural and controlled development. We could summarize it as "the container is the one you want and not the one you get". Hope it makes sense, if not feel free to comment on that thread. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com>
