I agree. However, one problem is to determine which requests that should be transaction demarcated. A configuration item?
There could be an EngineListener with serviceBegin/serviceEnd methods. /Per Norrman -----Original Message----- From: Eric Everman To: Christian Sell; Neil Clayton Cc: Norrman Per; [EMAIL PROTECTED] Sent: 2003-01-17 00:06 Subject: Re: [Tapestry-developer] Tapestry and O/R persitence services At 1/16/2003, Christian Sell wrote: >what about making this a generic hook in the framework proper, for anyone >who requires transaction demarcation. After all that is not an >O/R-specific issue.. Yes! This is really what my previous message was getting at. It doesn't need to be a hook for transaction demarcation specifically, but we do need a hook to mark the beginning and ending of a request, even if it crosses several pages. Does this exist and I'm just not seeing it? Eric Everman ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
