You are correct, since you haven't commited yet, the ejbStore call is still
pending for the entity bean...
Sounds like you need your entity bean to execute in its own transaction. You
could force this by having its transaction mode be TX REQUIRES NEW
-Chris.
> -----Original Message-----
> From: Gabriel Lawrence [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, October 18, 1999 10:57 AM
> To: [EMAIL PROTECTED]
> Subject: No checkpoint of EJB transactions?
>
> I've run into the following situation, and I'm wondering if I'm missing
> something, or if EJB is missing something... Any pointers would be
> great...
>
> I have an EJB Session Bean who has a method called approve(). In the
> approve method it finds a specific entity bean and changes a value on
> that bean. Next, inside the same method it executes a SQL command that
> makes use of the table from which the previous entity bean came from in
> addition to several other tables. What I've found is that since all of
> this occurs inside the same Transaction, and the entity bean doesnt
> update the database until the end of the Transaction is that when I run
> my SQL the change I've made to the entity bean hasn't been reflected in
> the database. This seems reasonable to me, as you wouldn't want to hit
> the database every time an Entity beans methods are called, but it seems
> to me that there should be a checkpoint command that flushes things to
> the database, but doesn't end the transaction...
>
> Am I just going about things the wrong way, is there a bug in my EJB
> server, or is there a bug in EJB spec, or did I miss something and this
> functionality is already there somewhere?
>
> thanx!
> -gabe << File: Card for Gabriel Lawrence >>
===========================================================================
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".
