In addition to the existing Enterprise JavaBeans (EJB) caching options, you can
develop read-only entity beans.
About this task
You are most likely to want to use it under the following
conditions:
- Your application uses data that change relatively infrequently.
An example might be a retailing application that uses pricing data
that only changes once a week or month.
- Your application can tolerate data that might be stale. The degree
of staleness allowed by the EJB container is configurable by
the user.
- The bean is coded in a thread-safe manner, so it can safely be
invoked by multiple threads at once.
To use this function, declare the bean type as read-only.
Declaring a bean type is done the same way that bean caching options
are selected - through a selection list within an assembly tool.
To
complete this task see the topic, Defining bean cache settings for
a bean in the assembly tool information center.