I actually reverted the changes from 2.3.0 and 2.2.2 (I'll change the fix versions field) because the change wasn't kosher with regards to the spec.
On Wed, Jul 10, 2013 at 11:08 AM, Romain Manni-Bucau <[email protected]>wrote: > Not the same case since i'm in eager mode for the relationship and it still > doesn't work on the 2.3.0-SNAPSHOT > > *Romain Manni-Bucau* > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > *Blog: **http://rmannibucau.wordpress.com/*< > http://rmannibucau.wordpress.com/> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* > > > > 2013/7/10 Rick Curtis <[email protected]> > > > I'm not 100% certain that I'm following your scenario, but I worked on a > > JIRA[1] a while back that sounds pretty similar. > > > > [1] https://issues.apache.org/jira/browse/OPENJPA-2285 > > > > Thanks, > > Rick > > > > > > On Wed, Jul 10, 2013 at 10:33 AM, Romain Manni-Bucau > > <[email protected]>wrote: > > > > > Hi, > > > > > > with a colleague we noticed today this behavior: > > > > > > 1) we activated the L2 cache > > > 2) we have an entity Foo with a relationship 1-n in eager mode > > > 3) we test the cache is correctly use > > > a) we call em.find(Foo.class, id) -> entity is cached but not the > > > relationship so a query is generated for each find > > > b) if we replace the em.find() by a query "select by id" all works > > > fine (cache is used and we don't see any query then) > > > > > > > > > Any idea? > > > > > > *Romain Manni-Bucau* > > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > > *Blog: **http://rmannibucau.wordpress.com/*< > > > http://rmannibucau.wordpress.com/> > > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > > *Github: https://github.com/rmannibucau* > > > > > > > > > > > -- > > *Rick Curtis* > > > -- *Rick Curtis*
