Nope, with the old code, B would be removed from the cache when b.remove()
was called even if it was invoked from within a transaction. Also, all
beans involved with a transaction would be removed from the cache on a
rollback within InstanceSynchronization.
I think that is the safe and correct approach to remove any bean from the
cache that is part of a rollback. Otherwise you may have corrupted data.
Bill
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of marc
> fleury
> Sent: Tuesday, July 03, 2001 2:57 PM
> To: Jboss-Development@Lists. Sourceforge. Net
> Subject: [JBoss-dev] remove transactional
>
>
> as I wrap up the stuff, sanity check
>
> bean a and bean b
>
> a starts transaction and calls b.remove() and then rolls back
>
> b is still there in cache right?
>
> marcf
>
> _________________
> Marc Fleury, Ph.D
> [EMAIL PROTECTED]
> _________________
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
