I've had this happen a couple times now where trying to proxy an
object the AopProxyUtils cfc writes an invalid fnct_*.function file.
Here's an example (notice the partial function after then end of the
first - legit - function):
<cffunction name="fnct_A83097A4D0825D02EA43546FA1DBBBAB"
access="public" returntype="void" output="false" >
<cfargument name="recipientservice" type="any" required="true" />
<cfset var rtn = callMethod('setRecipientService', arguments) />
</cffunction> returntype="void" output="false" >
<cfargument name="galleryId" type="numeric" required="true" />
<cfargument name="imageIds" type="string" required="true" />
<cfset var rtn = callMethod('splitGallery', arguments) />
</cffunction>
More confusing, the two functions aren't the same, which made me think
"race condition" on the file ops. I added an exclusive CFLOCK on the
filename around the 3 file operation lines inside createUDF but that
didn't fix the issue. I can't say for sure, but I believe the couple
previous times the "extra" stuff started with the returntype attribute
as well, though that may just be coincidence.
Anyone else seen this?
cheers,
barneyb
--
Barney Boisvert
360.319.6145
Got Gmail? I have 100 invites.
