Posted in ColdFusion | Posted on 08-24-2010 | 1,999 views
Watch out for this one - I almost didn't notice it. Today I went to add a new mapping. It just so happened that the mapping I added was one that already existed. The administrator correctly noticed this and gave me an error:
No big deal, right? I'll just rename mine to /org2 and hit submit.
Ouch. It actually replaced my org mapping. Not the end of the world, but if you had a lot of mappings it could easily be missed. Note - I recommend - almost always - that you use Application specific mappings. In my case though it is a code base I can't modify just yet.
I have filed a bug report for this, but unfortunately the public bug base still hides 901 bugs.


I logged it ages ago but it's not been fixed yet.
remote.service
and /remote/service.cfc used createObject("component", "com.goo") where com is a mapping - would that work? See the difference?
It's apparently in the mapping between a Flex value object (UserVO.as) to the remote ColdFusion value object (User.cfc), apparently it fails when it tries to lookup the mapping in the alias definition: [RemoteClass(alias="com.contactManager.security.user.User")]
Here's the full details on the reported bug: http://cfbugs.adobe.com/cfbugreport/flexbugui/cfbu...
[Add Comment] [Subscribe to Comments]