Hey Marc,
the caches (stateful and entity) run fine, jbosstest passes cleanly. There
is still an open issue:
in CMT TX managed beans (both stateful and entity) there is the possibility
that after the instance int'r unlocks the context and that *before* the tx
int'r lock it again in the Synchronization implementation, the passivation
for it occurs.
It can be solved by adding another flag in EnterpriseContext that tells that
a Synchronization has been registered (and thus will be called later) and
delay the passivation if this flag returns true (I already do a similar
check with EnterpriseContext.lock()), but maybe you've better ideas.
Best Regards,
Simon
