If you're using Commit option 'A' and you've accessed the bean through EJB then changed it in sqlplus, the entity bean will be cached and will synch with the DB. Use Commit option 'B' or 'C'. Bill > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of David > Ward > Sent: Friday, July 27, 2001 5:13 PM > To: Jboss-development > Subject: [JBoss-dev] Re: jboss not sync'd with external db changes - > OOPS > > > Oops - sorry. Should have sent this to jboss-user. I'll do that now... > > :( > David > > -- > > David Ward wrote: > > > I'm goin' a bit crazy here... > > > > If I have a sqlplus window open to my Oracle database, I can see the > > data change as I change values via my CMP Entity Bean. However, if I > > change a value in the DB using sqlplus (and commit it), my already > > active CMP Entity Bean doesn't pick up the change (it still has the old > > value). > > > > What am I doing wrong? I've attached my jaws/ejb-jar/jboss xml files. > > I'm going to look real stupid if it turns out the kind of synchronicity > > I'm looking for isn't supported... > > > > Thanks, > > David > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
