Hi,

I have a set of persistent objects, TaskPriority, which I preload when the server starts (in a HashMap)

Each call from the client implies a new session, while the caching was done in another session. Is that dangerous?

Now I get:

java.lang.NullPointerException: not-null property references a null or transient value: Task.priority

...when I save() on an object referrering to the previously cached priority object, despite the fact that the priority object has a valid ID.

Any ideas?

Uhm... yes, caching the stuff in the same session solved the problem, but that defeats the purpose of the caching...

How can I cache in one session and add cached objects in another? Cached objects never change.

Thought saveOrUpdate would help, but it didn't

Ideas?

Look into the new, lightweight HashtableCacheProvider and query caching functionality, using Query.setCacheable(true).

Jeff

Since the object has been saved previously, then you must update it instead of saving it. So saveOrUpdate would help if unsaved-value is set properly and the id is not assigned.

However, the first session must be flushed before the second one access to it. Otherwise, the second session will query a non updated DB