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
begin: vcard fn: Gabriel Lawrence n: Lawrence;Gabriel org: Kovair<br>The power to .wow your customers. adr: 2 North First Street ;;Suite 212;San Jose;Ca;95113-1202;USA email;internet: [EMAIL PROTECTED] title: Architect tel;work: (408) 491-9731 note: The power to .wow your customers. x-mozilla-cpt: ;0 x-mozilla-html: FALSE version: 2.1 end: vcard
