Hi Shelly,
According to the spec, your business methods must not interfere with the
container's demarcation of transactions, ie you must not use
javax.transaction.UserTransaction or java.sql.Connection interfaces.
If the automatic managing of transactions provided by the container (according
to the TX_Attribute) is not enough for you, I think what you can do in your
bean is invoking setRollBackOnly() or getRollBackOnly() on its EJBContext, but
you don't need to implement them (your Container provider has kindly done that
for you).
Benjamin
Shelly Aggrawal a �crit :
> hi all,
> i am using container managed demarcations for handling the transactions.
> is specifying thje TX_Attributes enough
> or do i need to implement the UserTransaction interface to do operations
> like
> setRollBackonly() which prevent the transaction from rolling back.
>
> ..................................
> Shelly Aggrawal,
> KPIT Systems Ltd., Pune.
> e-mail [EMAIL PROTECTED]
>
> ===========================================================================
> 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".
===========================================================================
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".
