• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

when to use the bean-managed persistence ejb?

 
Ranch Hand
Posts: 94
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Ranch Hand
Posts: 166
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, Forrest,
Actually, it depends on the EJB container, what persistance storages are supported. I don't know containers that support something other than RDBMS.
To add to your list, I would mention using BMP over CMP when you need a support for several databases in the app. CMP can work only with one at a time.
 
Forrest Xu
Ranch Hand
Posts: 94
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Actually, it depends on the EJB container, what persistance storages are supported. I don't know containers that support something other than RDBMS.

Thank you for your reply. This is what i concerned. I don't know containers that support something other than RDBMS either. I guess it does not support non-RDBMS.
The database the EJB container supports must be RDBMS or Object DBMS. but i am not sure.
Please help me.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic