Hi,
There's certainly no shortage on demand for features. Another small one is this:
A small annoyance and not something really new. Currently everyone who needs the TransactionManager just iterates over every known implementation (WebSphere, WebLogic, JEUS, OC4J, Geronimo, GlassFish, ...) and attempts to get it that way. It's just ugly, and the defence that "we" should not obtain the TransactionManager is moot, since we get it anyway now and have been doing that for 2 decades.
Additionally if I'm not mistaken UserTransaction still doesn't support @Inject, but needs the ancient and overloaded @Resource for injection. To align with the platform goal of moving to CDI, UserTransaction should be injectable with @Inject. At least Quarkus already supports this.
Of course, the issue is indeed about who's actually going to do the work. I'm fine with adding @Inject / BeanManager lookups for TransactionManager and UserTransaction to the spec and taking care of the implementation in GlassFish.
Maybe a bit too soon, but we could also be thinking about landing MicroProfile LRA in Transactions?
Kind regards,
Arjan Tijms