Nope, with Hibernate you can also call size() on the collection (the only difference between OpenJPA and Hibernate in that regard is OpenJPA returns null and Hibernate returns LazyLoadingException).
-- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Fri, Jun 27, 2014 at 5:22 PM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > actually that's worse. Depending the provider and the model to force the > loading you have to: > 1) do nothing (if eclipselinks has still the collection) > 2) call any collection method (openjpa) > 3) iterate over the full collection and call a method on all items (don't > recall exactly if that's hibernate or a particular model with eclipselink) > > > You can also just use a stateful as backing bean which keeps track of the > bean until @Remove method is called. > > > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > 2014-06-27 17:17 GMT+02:00 hwaastad <he...@waastad.org>: > > > Hi, > > thx for answering. > > > > the alternative would be a join fetch on queries, but it seems strange if > > this behaviour is not configurable. > > > > If it is, then it's easier to do migrations step by step. > > > > br hw > > > > > > > > -- > > View this message in context: > > > http://tomee-openejb.979440.n4.nabble.com/tomee-eclipselink-openjpa-tp4670212p4670217.html > > Sent from the TomEE Users mailing list archive at Nabble.com. > > >
