My understanding is that entity beanmethods, inorder for the container to
ensure consistency between the bean's state and the dabase, need to be
transactional. Yet, it appears that you can choose a transaction attribute for
an entity bean of NEVER or NOT_SUPPORTED. Isn't that, for all practical
purposes, the same as not running a method of an entity bean in the scope of a
transaction? That would mean that I could in fact update data in my entity bean
without the container ever commiting it because I did so outside of a
transaction, and the container therefore would fail to keep the bean and data
store i sync, n'estpas? Thanks.
Ken
===========================================================================
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".
