|
| Stateless Session Bean Replication |
 |
Tue, 13 Nov 2007 06:27:40 -080 |
In the WLS 10 documentation section "Replication and Failover for EJBs and
RMIs" the following statement is made about the state replication of
stateful session beans:
As the client makes changes to the state of the EJB, state differences are
replicated to the secondary server instance.
What exactly is the trigger for the replication? And what is getting replicated.
The documentation goes on to say: only the actual changes to the EJB's state are
replicated to the secondary server
How does the container know what changed? The reason I am asking these questions
is that I would like to know if there are any programming considerations that
need to be made to account for state replication as there are for HttpSession
replication where you need to make sure you call setAttribute again to trigger
replication in cases where you obtained an object from the |
| Post Reply
|
|
|
|
|
|
|
|
|
|