-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: Second level cache is not updated
PostPosted: Tue Mar 27, 2012 11:53 am 
Newbie

Joined: Tue Dec 27, 2011 1:33 pm
Posts: 4
I don't have much hope, just trying to find workaround:

there are 2 classes, Vendor(parent) and User(child). Vendor has collection of Users, User knows about Vendor. Collection of Users is mapped using inverse="true". All of these are in 2nd level EHCache: Vendor, Vendor.users, User, User.vendor.

Now, I add new user and associate them with Vendor like: user.setVendor(someVendor). Then, I update user. Because users are mapped inverse, all these are ok. But, Vendor.users collection which is in 2nd level cache isn't updated/invalidated. So, until cache expires, vendor doesn't know new user has been added to him.

Is there any way to manage this issue?


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.