The reason I believe that the cflock was necessary was based on the observable behavior of the site (the account bean was getting the wrong values set for its properties). The account bean wasn't just getting garbage values set, it was getting set to the account information for other valid...
Consider this original function in a CF component:
<cffunction name="getAccount" output="false" returntype="any">
<cfargument name="event" type="MachII.framework.Event" required="yes" />
<cfscript>
var account = createObject("java","com.mycompany.user.Account").init();
// gets...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.