Caching data at the ejb teer level

The system must provide 2 different web applications, 2 daemons (startup classes in weblogic) and probably a swing style client. To optimize accesses, some data, like configuration tables could be shared by all clients sessions. As the EJB specification explains, the session beans can't be shared by multiple clients, and containers should return exceptions when receiving simultaneous requests for the same session remote object. The data to be shared don't really fit the entity model, will not be probably read from a db but possibly from a ldap directory, and will be seldom updated.

What is the better design model to implements this kind of shared cache ?

[684 byte] By [Ephemeris-Lappis] at [2007-9-26 4:22:34]