I copy and paste the following case.
Can any one put more?
One question: if the database is not RDBMS, can we use container-Managed Persistence Entity Beans?
Despite the many advantages of container-managed persistence, there are situations in which it is more appropriate to develop entity beans using the bean-managed persistence approach. These include the following:
Use bean-managed persistence when you need exact control over the database schema or need to customize code to match a specific legacy database schema.
Use bean-managed persistence when it is important that the application be very finely tuned against the database that is in use.
Use bean-managed persistence when portability is not an issue. Even in this case, however, it is recommended that data access objects (DAOs) be used. DAOs better enable the bean to be adapted to a different database schema or to evolve into an entity bean with container-managed persistence at a later date. See Section 5.7.5 on page 160.
Use bean-managed persistence when the query needs of the application exceed the current capabilities of
EJB QL. While EJB QL will continue to develop, it is not yet able to express a number of queries that are expressible in SQL.
Use bean-managed persistence when your persistent store is not a database system or is a legacy database system that is not likely to be supported for container-managed persistence.