Today I began migrating some of our applications to ColdFusion 2018 (from ColdFusion 2016).
Things went pretty smoothly until I ran into this error:
Could not find the ColdFusion component or interface XXX.XXX.mycfc"
Where “XXX.XXX.mycfc” is a ColdFusion component.
In my case the component definitely exists and was in the path where it was being instantiated.
After a little troubleshooting and head scratching I decided to simply try adding a mapping in Application.cfc.
Magically the component could be instantiated and the application runs as it always has.
I have no idea why a mapping is now required in the latest version of ColdFusion.
An information technology professional with twenty four years experience in systems administration, computer programming, requirements gathering, customer service, and technical support.
0 Comments