In addition to the existing 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 may be stale. The degree of “staleness”
that the EJB container allows 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, you declare the bean type as read-only the
same way you currently select the bean caching options, through a selection
list within the application assembly tooling (either WebSphere Application
Developer or the Application Server Toolkit).