Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Developer's Guide

- Previous: Read-Only Bean Characteristics and Life Cycle
- Next: Refreshing Read-Only Beans

## Read-Only Bean Good Practices

For best results, follow these guidelines when developing read-only beans:

- Avoid having any `create` or `remove` methods in the home interface.

- Use any of the valid EJB 2.1 transaction attributes for the `trans-attribute` element.

  The reason for having `TX_SUPPORTED` is to allow reading uncommitted data in the same transaction. Also, the transaction attributes can be used to force `ejbLoad`.

- Previous: Read-Only Bean Characteristics and Life Cycle
- Next: Refreshing Read-Only Beans

- © 2010, Oracle Corporation and/or its affiliates