to defend them a bit JCA API is full of boilerplate (IIRC there is even a "common-jca" module allowing you to write only "business") so it is often faster and more efficient (in term of maintenance/knowledge) to not use them + it allows your app to be responsible of the injections (and not @Resource) which is for some teams what is looked for. As usual not the silver bullet
Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2015-02-11 10:57 GMT+01:00 Anthony Fryer <[email protected]>: > Jean-Louis MONTEIRO wrote >> JCA (outbound connection pool with transaction support) >> >> >> Very cool part of Java EE but not well known. > > So true. I've actually never met anyone in person that has built a JCA > adapter. Most people try to solve the problem JCA solves by re-inventing > the wheel and usually because they just don't know what JCA can do for them. > > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Just-curious-what-parts-of-JEE-is-everyone-using-tp4673713p4673747.html > Sent from the TomEE Users mailing list archive at Nabble.com.
