You must bind the stateful parameter to false. See the discussion of "running stateless" in the developer's guide.
Tapestry attempts to run in a stateless mode initially, i.e., no HttpSession. Much better for scalability and fast startup of the application. ----- Original Message ----- From: "Chris Merrill" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 03, 2002 8:46 PM Subject: [Tapestry-developer] stale sessions > I have a page that uses a Direct component. Whenever > I click that link, I get a "Stale session" error - I > don't think I'm ever getting to the Direct listener > (System.out.println() output is not seen). I found > a reference somewhere that indicates that I must have > a session in order to use Direct...but I don't seem > to see how to get a session. When I call getVisit() > it in the page constructor I get a null-pointer > exception. At this point in my app I haven't done > anything else that would require state: do I need to > force session creation earlier? What am I missing? > > ********************************* > Chris Merrill > [EMAIL PROTECTED] > ********************************* > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
