EJBLocalObject in a Clustered environment.

Let's assume that we have a huge project developing a J2EE app. We make lots of use of EJBLocalObjects well aware that the servlets and EJB's will execute in the same JVM. At some point in time, we decide to deploy our app in a cluster that supports HTTP session failover.

The fact that servlets and EJB's run in the same process will still be true. We never make interprocess calls to our EJB's. My concern is, if I have a EJBLocalObject stored in my HTTP session, what will happen when that session is serialized and deserialized? Is the reference between this object and the EJB container reestablished? Does the J2EE standard enforce this in any way?

[671 byte] By [thhala] at [2007-9-28 2:38:31]
# 1

Clustering is not specified so you might want to mention which vendor you are using. For Weblogic - "clients of a local bean must be in the same .ear file or same .jar file. Even if you are only looking them up on the same server, they may not be referenced across application boundaries. So, you may not store them in the global JNDI tree."

swatdbaa at 2007-7-7 22:11:14 > top of Java-index,Other Topics,Patterns & OO Design...