Hi, May an Entity Bean have transient attributes wich are set via the remote interface and so they are not "recomputable" in the ejbActivate()-method?
In JBoss 3.2.1 I have the phenomenon that those transient attributes suddenly appear in another bean instance after a passivation/activation cycle. I think this has to do with JBoss instance handling. It seems a passivated instance is reused for other Beans of the same type. Is there a configuration parameter to adjust this behaviour? In 3.0.6. everything run fine - probably not quite J2EE compliant.