Re: onSessionEnd not working as expected

2011-06-23 Thread Gerald Weir
Dan, Thanks (belatedly) this worked. Jerry ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/mess

Re: onSessionEnd not working as expected

2011-06-17 Thread Dan G. Switzer, II
Jerry, On Fri, Jun 17, 2011 at 11:55 AM, Gerald Weir wrote: > > First, my apologies to all if this is a duplicate post. I seem to be having > trouble posting. Anyway, > > Hello All, > > Thanks for your input. Ray, you are correct in that I needed to pass in the > session scope variables cor

Re: onSessionEnd not working as expected

2011-06-17 Thread Gerald Weir
First, my apologies to all if this is a duplicate post. I seem to be having trouble posting. Anyway, Hello All, Thanks for your input. Ray, you are correct in that I needed to pass in the session scope variables correctly. In my original post it is clear that a) I was not passing in th

RE: onSessionEnd not working as expected

2011-06-15 Thread Andrew Scott
The answer is in your own post, but as you don't share the code for onSessinEnd() and don't tells us what error you are getting then it makes it hard to help. On the surface, what is the problem. Is it that when you put the component in a directory it doesn't work or what? But if this is the case

Re: onSessionEnd not working as expected

2011-06-15 Thread Sean Corfield
On Wed, Jun 15, 2011 at 9:19 AM, Raymond Camden wrote: > If you are using session.ANYTHING, you will get an error. In > onSessionEnd, you must use the Session scope as it is passed in as n > argument. So arguments.sessionData.whatever instead of > session.whatever. What Ray said: session scope h

Re: onSessionEnd not working as expected

2011-06-15 Thread Raymond Camden
If you are using session.ANYTHING, you will get an error. In onSessionEnd, you must use the Session scope as it is passed in as n argument. So arguments.sessionData.whatever instead of session.whatever. On Wed, Jun 15, 2011 at 11:17 AM, Gerald Weir wrote: > > Just for testing I moved my CFC wit

Re: onSessionEnd not working as expected

2011-06-15 Thread Gerald Weir
Just for testing I moved my CFC with the "real" code to write the session.array to the database up to the root level so that I could identify the component as component="jobState". That way I could test the CFC itself without worrying about the location. So, calling the real component/method

Re: onSessionEnd not working as expected

2011-06-15 Thread Raymond Camden
I'd love to say I planned that. ;) On Wed, Jun 15, 2011 at 11:04 AM, Dave Watts wrote: > >> You asked this on SackOverflow as well. > > I just want to state for the record that I enjoyed this typo. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > http://training.figleaf.com/ >

Re: onSessionEnd not working as expected

2011-06-15 Thread Dave Watts
> You asked this on SackOverflow as well. I just want to state for the record that I enjoyed this typo. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest ca

Re: onSessionEnd not working as expected

2011-06-15 Thread Raymond Camden
You asked this on SackOverflow as well. I'll repeat my answer. I know I've seen folks use / in component calls before, but I do not believe it is officially supported. You want to use a dot notation path instead, ala component="lib.components.jobstate" and assure that lib is either a subdirecto