You're not exectly doing anything wrong, but there are a couple of things you can do to alleviate your problem. Short answer(s): 1. Implement a method 'boolean isModified()' on your entities that returns true if any field has been modified. The simplest way to implement this is to just have a modified flag that gets set to true in any setter, and set to false in ejbLoad, ejbStore, ejbActivate, ejbPassivate. 2. Are you calling entity beans directly from your client? If so, realize that each of those calls is a transaction, and even with the optimization above and commit option A (setting in jboss.xml/standardjboss.xml - default BTW), you're getting an awfull lot of overhead there. Consider adding a layer of stateless session beans to mediate access to your entities, or at least add "bulk accessor' methods - getter and setter methods that return and take (respectively) a data object containing all of the fields that your entity does. -danch Robert Finneran wrote: > The JBoss container seems to call ejbStore() on my BMP-style entity bean > very often. > This results in multiple unecessary UPDATE's to my base table. > > When does JBoss decide it should call ejbStore()? > > I must be doing something wrong! Any ideas would be very much appreciated! > > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
