cause it is breaking the compat even if fine in 90% of the apps instantiating the EMF after cdi. You can need JPA before CDI or CDI after JPA, both cases are valid and we can't handle both
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> 2017-03-10 19:17 GMT+01:00 Andy Gumbrecht <[email protected]>: > If this is the case, why is tomee.jpa.factory.lazy=tue not the default? > I'm guessing this will be an issue for anyone using hibernate. > > Andy. > > > > On 08/03/2017 20:22, DonatasCiuksys wrote: > >> Yes, with property tomee.jpa.factory.lazy=true it started to work. >> Thank you very much, Adam! >> >> >> >> -- >> View this message in context: http://tomee-openejb.979440.n4 >> .nabble.com/VOTE-Apache-TomEE-7-0-3-tp4681228p4681238.html >> Sent from the TomEE Dev mailing list archive at Nabble.com. >> > > -- > Andy Gumbrecht > https://twitter.com/AndyGeeDe > http://www.tomitribe.com > >
