Entries Tagged as “Adobe ColdFusion Builder”

CodeChef - ColdFusion Builder extension to speed up CFML coding

August 11, 2015 / Sandeep Paliwal

  Adobe ColdFusion | Adobe ColdFusion Builder | CFBuilder | productivity | Rapid Application Development

CodeChef which Is available on github is a ColdFusion Builder extension to help you make you very productive in your CFML coding.


What is CodeChef?

CodeChef(as the name suggests) cooks up CFML code for you in no time. Just type in kewords related to what you want to do and you are done. Keyword can be a use cases like “write”, “read”, “create” etc. just a keyword like “file”, “pdf” etc. Once you type keywords in the search filed CodeChef presents you with various options based on it. You select the option based on your requirement and just hit enter. That’s it!!. Basic CFML code related to the selected option will be added to the file currently open in editor.

How to Run the Extension

Just select Code Chef from dynamic Views drop down and click Show View to get started.
Once Code Chef view is launched just type the action/keyword in Code Chef view (ex. write file, create pdf, loop, or get current directory), select appropriate option from suggestions and hit enter. Appropriate code will be inserted in any file already open in editor. Here is a screenshot of CodeChef view in ColdFusionBulder showing various options for a given keyword










The current version is only a working prototype with limited options just to demonstrate the idea and its power. Here are few screenshots to give an you an idea. Download the extension and give it a try.


As I mentioned its just a working prototype right now so the options are not extensive. I will try to keep adding more code options and keep the project getting better and make CodeChef a really powerful CFML development tool. I will write another post on how once can contribute to add more options to it but since its just CFML and XMl it will be easy to figure it out.

Do give it a try.


When should tools.jar be updated in ColdFusion Server

July 27, 2015 / Krishna Reddy

  Administrator | Adobe ColdFusion | Adobe ColdFusion 10 | Adobe ColdFusion 11 | Adobe ColdFusion Builder | General

tools.jar contains the utilities to compile java source into class files.

While using ColdFusion Web services stubs have to be generated.

So, this utility is required for this feature to be functional.

The tools.jar is shipped by default with ColdFusion along with full installation of ColdFusion which would be same version of the jre that ColdFusion is shipped with.

If you are just using this default installation and the built-in jre, your ColdFusion web services do work fine.

However, due to security bugs or platform support you would want to update the jre version that ColdFusion runs on.

Once you do that, please make sure to copy the tools.jar file manually from {JDK_Home}/lib to {cf_install_home}/cfusion/lib/

Only JDK contains the tools.jar file not the jre installation. You don't have to install JDK on the machine where ColdFusion is installed. You can just have jre on this machine and get tools.jar from any other machine's JDK installation.

And also make sure that the earlier stubs are cleared from {cf_install_home}/cfusion/stubs/ to get the newly compiled classes.

It is necessary to update tools.jar ONLY if you are upgrading the jre to a a higher major version.

Say, if you are upgrading from 1.8 U5 to 1.8 U51 you don't have to update tools.jar file.

But, say   if you are upgrading from 1.7 U55 to 1.8 U51, you have to update tools.jar file.


Another case where you would want to update the tools.jar is JEE deployments.

Say, if you are using Websphere application server with IBM JDK, you have to place the corresponding JDK's tools.jar under  {cf_install_home}/cfusion/lib/.

The same applies to any other application server as well.

The simple rule is that tools.jar has to be from the same major version of Java (minor version doesn’t matter) that ColdFusion runs on.


This applies to any version of ColdFusion and the same applies to all platforms.

You can copy tools.jar from Windows machine to Solaris macine as well as long as the version is correct.



Some of the factors that help in deciding the memory that application needs

July 27, 2015 / Krishna Reddy

  Administrator | Adobe ColdFusion | Adobe ColdFusion 10 | Adobe ColdFusion 11 | Adobe ColdFusion Builder | ColdFusion | ColdFusion 11 | General

Would like to explain the some of the factors that decide how much maximum memory that an application needs.

Here are two examples. One is with cffile upload action and the other is with cfpdf thumbnail action.

Sometimes, while uploading large files using cffile with upload action (<CFFILE ACTION= "UPLOAD") you would have run into the following error

"500 - Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed."


File upload is dependent on “Maximum size of post data” value that you can set in ColdFusion Administrator.

However, it can’t exceed the total available free memory.

Say, if 512 MB is the Xmx memory value (jvm.config) and 350 MB is already occupied by the application, even if “Maximum size of post data” value is set to 200 MB, it can upload files of up to ~150 MB (512 MB- 350 MB).

It can’t upload files of size 200 MB.

To fix it, Xmx should be increased which is again subjected to the available memory in that machine.


Here is other example:-

Say, you are using CFPDF's Thumbnail Action and the thumbnails background is not generated properly.
Here the issue would be insufficient memory.

        Just to hold the decoded image data, java application needs large memory (say 1.2 GB depending on the image pixels).

It is because of the format and high pixel nature of the image that is being converted. Number objects created are equal to the total number of pixels in that image.

So, high pixel imge would consume more memory.

To fix this, Xmx value in jvm.config should be at least -> Applications memory Size + 1.2 GB (from the above example) i.e. a minimum of 1.5 GB and can be more depending on your application.

Changing the value and restarting the server would fix this.

How to enable/disable Tomcat logs

July 26, 2015 / Krishna Reddy

  Administrator | Adobe ColdFusion | Adobe ColdFusion 10 | Adobe ColdFusion 11 | Adobe ColdFusion Builder | ColdFusion | ColdFusion 11 | Tomcat

Sometimes, depending on your need, you may want to enable or disable the tomcat logs.

This can be simply done changing a setting a in <ColdFusion_Home>\cfusion\runtime\conf\server.xml file.

At the end of this xml file you can see the following tag.


<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" 

               prefix="localhost_access_log." suffix=".txt"

               pattern="%h %l %u %t &quot;%r&quot; %s %b" resolveHosts="false"/>


Uncomment this tag as follows and restart the server for the changes to be effective.

<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" 

               prefix="localhost_access_log." suffix=".txt"

               pattern="%h %l %u %t &quot;%r&quot; %s %b" resolveHosts="false"/>

Similary, to enable the Tomcat logs, comment this tag.

When Tomcat logging is enabled, you can change the logging level in the logging.properties file by changing the following setting.

org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level = WARN



Configuring JNDI Data sources in ColdFusion

July 25, 2015 / Krishna Reddy

  Administrator | Adobe ColdFusion | Adobe ColdFusion 10 | Adobe ColdFusion 11 | Adobe ColdFusion Builder | Application Server | ColdFusion | ColdFusion 11 | General

For configuring JNDI data sources, it should firstly be supported by the application server.

Tomcat server, which is built-into ColdFusion server, has the support for this by default.

While there is a blog Here on this how to configure, I want to explain few mistakes that are tend to be done while configuring. 

  One common mistake generally done is:-
  When the data source is configured from the ColdFusion administrator by providing irrelevant    username/password.
  You may tend to provide Database's username/password. This is NOT Database's username/password.
  It is the application server's username and password on which data source is configured.
  It should be left blank when the credentials are not required by the server.

Prepending java:comp/env/ is required for the actual JNDI name that is registered in xml while registering the name in administrator.

It is not mandatory that you register the JNDI data source in ColdFusion administrator.

As long as the app server supports JNDI, you can invoke the data source that is configured in the application server in cfm source code directly either in case of standalone installation or EAR/WAR deployment.
But for consistency and preferred names that can used in ColdFusion should be registered in ColdFusion.

This is applicable to both ColdFusion 10 and ColdFusion 11.


Blue Mango Theme Design By Mark Aplet

Super Powered by Mango Blog