I am using hibernate behind a J2EE session beans layer and the hibernate session lives for the duration of the session bean call.

I was wondering how can I use a caching mechanism on the (J2EE)client side such that I minimize the RMI calls?

TIA,

--steve p.

What's the client? What are you returning from the session beans that you want to cache?

I return Hibernate POJOs and want to cache this objects so that when I want to get a domain object I could get it from the cache instead of doing the RMI to the JBoss server (which deals with the db)

thx.
--steve p.

Well you can do any kind of caching, keep a reference to previously loaded objects, plug in OSCache or whatever. Actually whenever you just display something to the user you are in practice allready doing "caching".

Be aware however that by doing such things you will run into really ugly data staleness problems in a multi-user environment. Doing cache invaldiation is allready ugly enough when using server-side caching, and becomes even more ugly when having caches on the client.

Yeah, if you cache on the client, you must use optimistic locking. See section 17.3.2 of the hibernate reference.

And if your client is a Servlet running in Tomcat, definitely use the Tomcat/JBoss combo. There's no RMI involved in making an in-JVM call to a JBoss session bean.