siriiven wrote:
>
> Any ideas?
>
Take a peak at the documentation. It describes all the ins
and outs...
you have to do the same thing with application variables as
session
variables. The hint being that you are also defining an
appScope
argument as well as the sessionScope argument, there is a
reason for this.
<quote
src="
http://livedocs.adobe.com/coldfusion/7/htmldocs/wwhelp/wwhimpl/common/html/wwhelp.htm?context=ColdFu...
Usage
Use this method for any clean-up activities when the session
ends. A
session ends when the session is inactive for the session
time-out
period or, if using J2EE sessions, the user closes the
browser. You can,
for example, save session-related data, such as shopping cart
contents
or whether the user has not completed an order, in a
database, or do any
other required processing based on the users status.
You might also
want to log the end of the session, or other session related
information, to a file for diagnostic use.
If you call this method explicitly, ColdFusion does not end
the session;
it does execute the method code, but does not lock the
Session.
You cannot use this method to display data on a user page,
because it is
not associated with a request.
You can access shared scope variables as follows:
You must use the SessionScope parameter to access the Session
scope. You
cannot reference the Session scope directly; for example, use
Arguments.SessionScope.myVariable, not Session.myVariable.
You must use the ApplicationScope parameter to access the
Application
scope. You cannot reference the Application scope directly;
for example,
use Arguments.ApplicationScope.myVariable, not
Application.myVariable.
Use a named lock when you reference variables in the
Application scope,
as shown in the example.
You can access the Server scope directly; for example,
Server.myVariable.
You cannot access the Request scope.
Sessions do not end, and the onSessionEnd method is not
called when an
application ends. The onSessionEnd does not execute if there
is no
active application, however.
</quote>