> The problem with session bean is, as far as I understand, every session
> is unique. So if I calculate the state in one session, then it won't be
> accessible next time I invoke the session bean, although the data has
> not changed. I can never get to the same session bean again, which
> defeats
Thanks for your kind reply!
[EMAIL PROTECTED] schrieb:
> What do you think about stateful session beans?
> For example, if you take the stateful session bean, you have the
> conversational state. Having the big cache you can expect that your bean
> will remain in memory. At least, when the bean
