This sample application shows how repeated calls to the same session bean have a persistent state -- the change in the cash account -- that is maintained across all the calls. Notice that neither the client nor the EJBean do anything to maintain that state: the container handles it transparently. All the logic for the cash account is encapsulated in the bean, unlike the statless session sample where all persistence is provided by the client.
