Hey (again
Chip Wilson wrote:
> 3) Let's say that I update two entity beans with BMP within the same
> transaction. I commit the transaction, and the container calls ejbStore on
> the first bean. This succeeds, and the container calls ejbStore on the
> second bean. During this call, the underlying persistent store rejects the
> update. Now, it would seem that there is no way to rollback the
> transaction. If the container calls ejbLoad on the first bean, it will load
> the data it just stored.
Please disregards my two last notes on this subject. It seems the
container is indeed allowed to passivate EntityBean instances during
transactions which would cause problems to beans using non-transactional
persistence managers in a transactional context.
So, the strategy outlined would only work if the EJB-server makes sure
that no beans currently in a transaction are passivated. This could be a
server-dependent feature that could be added in order to make the
strategy work. Good/bad idea?
/Rickard
--
Rickard �berg
Computer Science student@LiTH
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
