Editing Adobe ColdFusion (section)

=== ColdFusion and Java ===
The standard ColdFusion installation allows the deployment of ColdFusion as a [[WAR (Sun file format)|WAR file]] or [[EAR (file format)|EAR file]] for deployment to standalone application servers, such as [[Macromedia JRun]], and IBM [[WebSphere]]. ColdFusion can also be deployed to servlet containers such as [[Apache Tomcat]] and [[Jetty (web server)|Mortbay Jetty]], but because these platforms do not officially support ColdFusion, they leave many of its features inaccessible. As of ColdFusion 10 [[Macromedia JRun]] was replaced by [[Apache Tomcat]].

Because ColdFusion is a Java EE application, ColdFusion code can be mixed with Java classes to create a variety of applications and use existing Java libraries. ColdFusion has access to all underlying Java classes, supports JSP custom tag libraries, and can access JSP functions after retrieving the JSP page context (''GetPageContext()'').

Prior to ColdFusion 7.0.1, ColdFusion components could only be used by Java or .NET by declaring them as web services. However, beginning in ColdFusion MX 7.0.1, ColdFusion components can now be used directly within Java classes using the CFCProxy class.<ref>{{cite web|url=http://www.forta.com/misc/cfcproxy.htm|title=Using the CFC Proxy|access-date=2005-12-25|archive-url=https://web.archive.org/web/20051226115144/http://www.forta.com/misc/cfcproxy.htm|archive-date=2005-12-26|url-status=dead}}</ref>

Recently, there has been much interest in Java development using alternate languages such as [[Jython]], [[Groovy (programming language)|Groovy]] and [[JRuby]]. ColdFusion was one of the first scripting platforms to allow this style of Java development.