So can I be so bold as to ask for the correct code to be using so I
don't get that error with people using J2EE sessions?
Thanks!
Jake
Peter Tilbrook wrote:
I'd have to verify this again to be sure, but if you use J2EE session
variables I *believe* they're killed automatically when the browser
closes without doing any extra work (in other words, you use J2EE
session variables and this is the default behavior). The error you're
seeing when the J2EE sessions are enabled is because it uses a
different variable to define the session (jsessionid) so the typical
CFID and CFTOKEN aren't present in the session. I think all you'd
have to do to handle this would be to do a check for StructKeyExists
(Session, "CFID") and StructKeyExists(Session, "CFTOKEN") before doing
the cookie stuff. If they don't exist, don't do that cookie stuff and
you should be all set.
Wrong! CFID/CFToken are still present but the Java session ID is appended.
So all the rules for maintaining state with ColdFusion using CFID/CFToken
still apply.
Peter Tilbrook
ColdGen Internet Solutions
Manager, ACT and Region ColdFusion Users Group
PO Box 2247
Queanbeyan, NSW, 2620
AUSTRALIA
WWW 1: http://www.coldgen.com/
WWW 2: http://www.actcfug.com/
Telephone: +61-2-6284-2727
Mobile: 0432 897 437
E-mail: [EMAIL PROTECTED]
----------------------------------------------------------
To post, send email to [email protected]
To unsubscribe:
http://www.dfwcfug.org/form_MemberUnsubscribe.cfm
To subscribe:
http://www.dfwcfug.org/form_MemberRegistration.cfm
----------------------------------------------------------
To post, send email to [email protected]
To unsubscribe:
http://www.dfwcfug.org/form_MemberUnsubscribe.cfm
To subscribe:
http://www.dfwcfug.org/form_MemberRegistration.cfm
