Deploy your Session Bean so that it REQUIRES a transaction. Deploy your
Entity Beans to REQUIRE or SUPPORT a transaction.
Your Session Bean can use the SessionSynchronization interface to check the
condition, and vote rollback (through the JTS interface provided by your EJB
server) if the condition is not met. Or you could simply check the condition
in the Session Bean method that was called by the client after calling the
Entity Beans.
-Chris.
> -----Original Message-----
> From: Pascuzzi Domenico [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, December 13, 1999 6:23 AM
> To: [EMAIL PROTECTED]
> Subject: SESSION BEAN STATEFUL
>
> How can I model this situation with session and entity bean
>
> begin_TX
> op1 on entity bean1
> op2 on entity bean2
> op3 on entity bean1
> op4 on entity bean2
> op5 on entity bean1
> if (cond) commit
> else rollback
> end_TX
>
> What is the model to be used?
> What are the settings (transaction attribute) at deployment time?
>
> Pls, help me
>
> ==========================================================================
> =
> 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".
