Post a comment (login required)
The August 2005 issue of a prominent ColdFusion magazine wastes several pages on OO with ColdFusion. Let's face it, CFC's are about as object oriented as PHP4: neither are enterprise-ready. For one, they both lack the "Interface" construct, an absolute must for genuinely robust object oriented architectures. There are other shortcomings as well, but interfaces provide an acid test as to developers' understanding of objects: if you don't grok interfaces, you shouldn't be leading an enterprise OO project. All is not lost for ColdFusion however, it's advantage over PHP4 being it's foundation: Java. Let Java do the OO "heavy lifting", and then leverage the servlet API's getServletContext().getRequestDispatcher() functionality to subsequently forward both request and response to ColdFusion templates. OO with ColdFusion itself is not necessary to its continued thriving, rather it can provide the view component of MVC under Java.