Hi!


> |Excellent!  The only thing we have to do then is skip the sessionContext
> |in the passivation. (right now the passivation tries to read the field -
> |and fails.)
>
> and activation puts one right back right ???

No because the replacement mechanism needs something to replace... just
taking things away will just break it more, not fix it.

Again, the real fix is to serialize the bean and not the individual fields.

/Rickard




Reply via email to