http session object vs EJB Session bean


Web tier: servlets, JSP, Web frameworks: http session object vs EJB Session bean

  1. http session object vs EJB Session bean (3 messages)

    This application is a read only application and does not have any updates. The data read is large volume data for display. Can anyone suggest a good method to store all the returned values for future usage (any trade offs between storing them as http session object or creating a session bean and storin in session object)
  2. As I understand it, you're asking to have database data cached in the middle tier beyond a single transaction. If it's read-only data this is easily achievable via entity beans. An entity bean represents database data and can be cached by the application server. Most serious application server vendors provide some facilities for this.

    I believe that BEA, for example, has a simple entity bean caching mechanism that is useful if you have exclusive database access. There's a deployment descriptor flag called isDbShared, which instructs WebLogic to not call ejbLoad() on your entity beans. We use for this very web site and it works well. For larger systems you may not be able to get away with it. Other vendors have more advanced caching mechanisms that you may need to employ.
  3. http session object vs EJB Session bean[ Go to top ]

    I agree with you But the thing is you will have to have a remote call to access the data from the DB. I would appreciate if someone let me know is this the better way of designing. As remote calls are expensive
  4. What you are looking for is read-only entity beans:

    for example.

    -- t