This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes Standard way to handle Repository in JPA Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Standard way to handle Repository in JPA" Watch "Standard way to handle Repository in JPA" New topic
Author

Standard way to handle Repository in JPA

Mike Thompson
Greenhorn

Joined: Oct 28, 2010
Posts: 2
Hi All,

Consider the following scenario.

There is a table in db whose content together form as a repository. This table will be updated (updation of existing extities, addtion of new entities or removal of entities) rarely.
So currently the approach that I was using was to create a singleton XXXRepository pojo which will read all the rows (entities) from XXX table and store them in a map.

If someone is updating the XXX table then after the update part of code is executed, a post runnable will run which will clear the repository (map) and hence next time any entity is being located from the map, the loadRepository will be invoked (as the map will be null).

This the way I currently handle repository caching which I can use throught the application life cycle.

Is there any standard way provided/supported in JPA/Hibernate to achieve/implement this requirement.

I went through the caching mechanism (both 1st and 2nd level cache). But it seems to be for entities or queries or data and for different purpose/approach than what is expected to be happening or achieved by Repository.
Also if we are able to achieve this somehow by using 2nd level cache, then there is one more issue that cache updates only in case of jpa operations and jpql queries. In case of jdbc or native queries it will fail to be updated and we will have stale data (correct me if I'm wrong).

Please help me in this regards as what is the standard way to be followed in jpa for this.

 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Standard way to handle Repository in JPA
 
Similar Threads
Distributed Caching
Best mapping approach for reference/LOV/lookup data
efficient way to perform CRUD operation in Oracle TopLink
JDO Caching?