I might be mistaken, but I thought the web filter and getThreadDataContext() used the session (HttpSession)? My applications are session-oriented, so I definitely want a DC in the session somewhere. If you don't care about sessions too much, you can probably get away with creating a new DC every request.
/dev/mrg -----Original Message----- From: Jeff de Vries [mailto:[EMAIL PROTECTED] Sent: Thursday, June 08, 2006 4:37 PM To: [email protected] Subject: Re: Tapestry tutorial advice We use Tapestry 3, and just use the standard Cayenne web filter and DataContext.getThreadDataContext(). Works fine. Not really sure why you *want* to store the DC in the session ... Jeff Andrus Adamchik wrote: > I am reworking Cayenne tutorials for 1.2 final release. Since I > haven't used Tapestry for almost a year, and totally missed on 4.0, I > wanted to get some feedback from Cayenne/Tapestry users. What are the > good ways to bind DataContext to a session? > > Current example puts it in the visit. I would personally use a regular > web app setup with Cayenne filter (making Tapestry app just another > web app case as far as Cayenne is concerned). I wonder what others are > doing in this respect? Any HiveMind magic? > > Andrus
