O'Reilly logo

J2EE™ Applications and BEA™ WebLogic Server™ by Sandra L. Emerson, Rob Woollen, Michael Girdley

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Using Read-Only Entity Beans

As we've seen throughout this chapter, entity beans provide an object view of persistent and transactional data. However, not all persistent data is truly transactional. Many Web applications are dominated by reads and can even tolerate slightly stale data. The WebLogic Server offers an option called read-only entity beans to provide greater performance for read-intensive applications.

The advantage of read-only entity beans is that their data can be cached in memory, in many servers in the cluster. Read-only entity beans do not use expensive logic to keep the distributed caches coherent. Instead, the deployer specifies a timeout value, and the entity bean's cached state is refreshed after the timeout has expired. ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required