File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes EJB and other Java EE Technologies and the fly likes entity bean design for performance Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Make it so: Java DB Connections & Transactions this week in the JDBC forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "entity bean design for performance" Watch "entity bean design for performance" New topic

entity bean design for performance

Saha Kumar
Ranch Hand

Joined: Feb 23, 2006
Posts: 218
Hello All,
Once an entity ejb has been created, it corresponds to a record in the database and an entity EJB in memory. If the entity bean is not used for awhile, it may be passivated (cached to disc). My question is:

Once it is created, will it always either be in memory or cached to disc?

Also, when designing an EJB entity, is it useful for performance to separate changing data from static data? I am thinking that since the EJB is in memory, the database does not need to be accessed for the static data...only the changing data needs to be accessed via database.

Is this correct?

Thanks in advance.

I agree. Here's the link:
subject: entity bean design for performance
It's not a secret anymore!