Long transactions.

From the Roller-dev list:

Lance: Castor is *supposed* to be caching objects for us so that we don't need to make repeated calls to the database. I suspect the way we are using Castor may not be optimal, though I really don't know enough to suggest improvements.

Webapps seem to cause problems for O/R frameworks. In an O/R framework, things seem to work properly only inside of a O/R "transaction" or "session." In a webapp, you get an object from the database in one session, close that session, allow the user to modify the object in an HTML form, then start another session to update the object in the database. Castor calls this a "long transaction." I wonder how these long transactions effect Castor's ability to cache efficiently.

Dave Johnson in Java 02:34AM Feb 19, 2003 Comments [1]
Tags: Java

Comments:

There is actually a long article describing the issues with Castor and long transactions. May be of some help. http://www.spiderlogic.com/modules.php?name=News&file=article&sid=16

Posted by RefuX on February 19, 2003 at 02:36 PM EST #

Welcome

This is just one entry in the weblog Blogging Roller. You may want to visit the main page of the weblog

Related entries

Below are the most recent entries in the category Java, some may be related to this entry.