"Kenneth D. Litwak" wrote:
> This is what I thought. Transactions for session beans are really pretty
> meaningless, since no matter wwhat, the bean developer has to do all the work.
> A Ts that is CMT is only of real value for an entity bean.
Not true. It's true that there's no automatic rollback for session bean state,
but there is for entity bean state for any entity beans whose methods are within
the scope of the CMT. See my response on the thread "Transaction, entity beans
and passivation".
>From a design standpoint, it seems almost pointless to control transactions at
the level of individual entity bean methods. What you want more typically is to
have some session bean that needs to make a consistent set of changes to a number
of entities. That's the method that needs the Requires (or Requires-new)
attribute. You can put a Supports attribute on the entity bean methods.
John Collins
===========================================================================
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".
