You are not kidding, on an initial cut we gained 30% using the isModified(). These two questions came up; should modified be set to false on the setEntityContext and ejbStore methods? should there be some form of wrapper around it for transaction support? If the Tx fails is there any out for which I would want to leave the modified flag 'true'?
John
-----Original Message-----
From: Frank Marx [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 04, 2001 9:08 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] JBoss performance problems
Hi,
as far as I know the ejbStore() is called after you access a method of the
Entity Bean (no matter if reading or writing access),
because the container cannot find out if it is neccessary to update the
corresponding row in the DB Table, also there is a
Transaction started for the when you access a method of the entity bean.
You may implement the isModified() method to support the Container. We did
this and we gained a lot of performance.
I hope this helps.
Frank Marx
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
