finders are always done against the database.... so a finder will work. commit options will only after _changed_ rows - not _new_ rows (afaik)
cheers dim ----- Original Message ----- From: "JD Brennan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 21, 2002 11:01 AM Subject: RE: [JBoss-user] Server log in JBOSS3.0RC2 Perhaps you need to use Commit Option B or C instead of A which assumes there's no one else accessing the database and therefore is free to cache things. JD -----Original Message----- From: Stephen Coy [mailto:[EMAIL PROTECTED]] Sent: Monday, May 20, 2002 5:46 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Server log in JBOSS3.0RC2 I think you need to learn about transactions and commit options. On Tuesday, May 21, 2002, at 04:50 AM, Michael Delamere wrote: > Iīve got a stateless session bean doing a jndi lookup on my entity bean > and > returning an array of objects. The problem is that the first time I > start > the application everything works fine and I get all of the data > displayed in > my jsp without a problem. > > After the first call I manually enter a new record into the database. > When > I press refresh in the browser the new row isnīt shown. What could the > reason for this be? _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
