Benoit: Can you explain a bit more about why you need to do that?
In my experience, if you store an instance in the session struct, but don't actually refer to session/application vars inside of the component you should not run into the page context bug. For the components I have used cached in a session, I just private instance variables to hold any persistent data -- that way I preserve encapsulation and never have to work around the page context bug. I'd be curious to know what others are running into, though. - Nathan > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Benoit Hediard > Sent: Tuesday, March 25, 2003 11:46 AM > To: [EMAIL PROTECTED] > Subject: Page context bug workaround (was RE: [CFCDev] MVCF at > benorama.com) > > > The session.currentMember is an instance of > com.mycompany.member.MemberSession CFC. > > In order to wait for a fix of the Page Context bug (...), I'm using a > workaround custom tag called <cf_reinit> that allow me to get > back the page > context in Session CFCs. > > I don't remember where I got this <cf_reinit> custom tag... > I can send it to you off list if you wish. > > Benoit Hediard > www.benorama.com > > > > - Session CFCs that act as a facade to handle the client session > > > (statefull). > > > Ex. : > > > <!--- use the com.mycompany.member.MemberSession CFC put in session > > > scope ---> > > > <cfif session.currentMember.hasTheRightToDoThat()> > > > ... > > > </cfif> > > > > Is the CFC in the session or is a data structure produced by (and > > subsequently manipulated by) in the session? If the former, won't you > > hit the Page Context Bug? > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
