EJB design: Entity bean caching problem
Hi, I want to know if I JUST need read-only data. Do I have a performance benifit to implement it as entity bean? Since entity bean can cache the result set and use later, while using JDBC won't.
and how can I control the when to cache entity bean? The database contains those read only data MAY update by another Java program(daemon), and then send to web client as read-only data.
Can I control the entity bean to refresh its content when I know the data has been changed??