ejbStore is called by the container when it determines the state of your bean must be flushed to the datasource. If you want to control this synching, then you need to commit the current transaction. You can do this in a session bean using bean managed transactions, but generally this is not best practice. Why do you need to force the flush? Typically you should think in terms of synching at transaction boundaries with EJB. This is the norm... -Chris. > -----Original Message----- > From: Tarun Dewan [SMTP:[EMAIL PROTECTED]] > Sent: Friday, July 07, 2000 1:11 AM > To: [EMAIL PROTECTED] > Subject: Update in BMP > > Hi Guys, > > What I understand in BMP is that we can create an object of BMP EJB for an > existing record with findBy methods. But after updating the fields with > Set > methods, how can I update the data immediately as ejbStore() is called by > Container itself. Do I have to write some method of my own or it is > available. > > Thanks in advance. > > Tarun > > ========================================================================== > = > 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".
