James Sutherland wrote:I think you are probably making things more complicated than they need to be. Since JPA (EclipseLink) already maintains an object cache, you can probably do away with your Cache. That should simplify things considerably.
Just call find() with the id to find the entity, and if it is in the cache, it will not access the database. You will only need to call merge() if you have changed a detached object.
Testsuite: Standard testsuite
Executed on: Server1
Started at: 2011-10-10 10:11:24
TEST-1024 "Test with name X": Success
TEST-1025 "Test whit another name": Failure
Junilu Lacar wrote:Hi all,
I was just wondering if anybody out there has organized or participated in a study group for the certification exam. If you have, would you mind sharing your experience? What worked and what didn't? What would you have done to make the group study time more effective?
Steve Luke wrote:One thought is to replace the LatchGuardedMessage with a BlockingQueue. When you wait for a message you use either the take() or the poll(...) methods to get the next message out of the queue. When a new message comes in you add it to the queue with put(...). That way, if two messages come in consecutively the waiter will be sure to get the first message first, and not lose the second message.
Christophe Verré wrote:Eclipse Plug-ins, Third Edition is a great book to learn about Plug-ins development. The "Favorites" application made in this book would help you understand how to make your view.