Putting EJB reference into Http Session, clustering, any issues?


EJB design: Putting EJB reference into Http Session, clustering, any issues?

  1. We are using Weblogic 6.0 in cluster mode.

    There is a need to put a reference to a Stateful Session Bean into Http Session. There are 2 ways to go about it, either put the reference as is to the session, or convert the reference to a String, and put the String to session.

    Either ways, are there any issues with that regarding clustering.

    I believe Weblogic 6.0, supports Http Session failover.

    I would appreciate if someone be able to reply back soon.


  2. The best way will be to put a handle to your bean (it's fully serializable) if you really think that it's a good idea to store references to SFSB on client side, because I don't.

  3. Can you please tell me the reasons, why storing references to SFSB on client side is not a good idea?


  4. Interesting, you'd recommend not putting a reference or handle to a SFSB in the HTTP session? I can see how it's less than ideal, but offhand I can't think of anywhere else to put it between client requests (The JNDI store maybe, but that's awkward). Where yould you store it?

  5. But storing a Remote Object in Cache (whether it is in HttpSession or Static variables ) is not a good idea.