Flex deployment - maintaining session information.
Description
This relates to LDEV-987.
Not sure if this is a bug or a configuration issue but two of the three applications we currently run in ACF9 require session information to be available for the logged in user. Our applications authentication take place through standard CFML pages and this information currently persists over to the Flex app when running on ACF9. Running Flex on Lucee is not providing us with the same session capabilities.
Ref:
Ben Forta's blogs about flex remoting back in 2006 / 2007 prompted me to look at the remoting between flex and cfc's as apparently flex should be aware of session information by default through AMF.
http://forta.com/blog/index.cfm/2006/9/24/Flex-And-Session-State-Management
http://www.forta.com/blog/index.cfm/2007/11/15/Flex-And-ColdFusion-Session-Variables
informs me that AMF is no longer used for this purpose and should be handled through BrokerServlet / MessageBrokerServlet. I can't find any configuration information on this. Perhaps this is a bug and should just work without any further configuration?
Environment
Activity
problem seems unrelated to the session passed, problem is that the application.cfc not is executed.
Workaround:
in the sessions.cfc set the application data with help of the tag application as follows:
Problem solved.
Problem was in the extension, the method used to do a call was "execute" instead of "executeCFML". What did a lucee dialect call instea a cfml call. For Lucee dialect calls, Lucee looks for Application.lucee files instead of Application.cfc, so the application.cfc never was used.
This did happen because with Lucee 4.5 "execute" was the right method.
To fix your env execute ant on the new code in the repo, replace your existing lucee-flex-1.0.0.*.jar with the one newly build one.
That's excellent news . I look forward to giving that a go next week.
Many thanks for your help with this issue which now appears to be fixed!
There are a few other ACF / Lucee irregularities that still need to be fixed in our applications but we now have 2 out of the 3 applications working. I will get to work on the 3rd tomorrow.
There has been a public holiday in NZ on Monday so have only managed to get back onto this today.
Assignee
Reporter
Priority
