For anyone using ColdSpring to map Reactor objects to AS objects, remember that when setting up your FlashMappings in the config file, you need to use the final object that you wish to map, meaning you must specify the database-specific version of the object. Also, I had to modify line 54 of the
flashUtilityService.cfc to call the desired object.
It was:
<cfinvoke component="arguments.result" method="#mappings.getInstanceDataMethod(cfcType)#"
returnvariable="props">
It should be:
<cfinvoke component="#arguments.result#" method="#mappings.getInstanceDataMethod(cfcType)#"
returnvariable="props">
It seems to be working well now, and I'm going to try to get CS to play nice with an event gateway listener, using much the same methods as the remote service objects, but I'm having an issue where it appears that CS isn't injecting all my dependencies, but it is injecting some of them. I don't think that's what's actually happening, but it's a starting point. Ever feel like you're in a crime drama tracking stuff down sometimes? :) I'll do some testing and try to narrow that down and post the results later, in case anyone is trying something similar. Incidentally, I've set up my event gateway listener as a facade that gets CS from application scope, and then calls a method on a CS-injected bean, which calls a method on a CS-injected bean, which is where the failure appears to happen (that second bean isn't there.) I think ColdSpring is the new crack, I can't put it down! ;)
- [coldspring-dev] flashMappings caveat Ken Dunnington
- [coldspring-dev] flashMappings caveat Kurt Wiersma
