Skip to main content
Ben Nadel at InVision In Real Life (IRL) 2019 (Phoenix, AZ) with: Scott Markovits
Ben Nadel at InVision In Real Life (IRL) 2019 (Phoenix, AZ) with: Scott Markovits ( @ScottMarkovits )

Returning NULL Values From A ColdFusion User Defined Function

Published in Comments (8)

For those of you have worked with any of the underlying Java methods in ColdFusion or worked with the installed Java libraries, you probably know that Java returns NULL values a lot of the time. And, furthermore, you'll know that if a NULL value is returned, ColdFusion deals with this event by destroying the variable into which the NULL value is stored. Once you understand this, it makes dealing with Java a lot easier.

Of course, up until now, I have only ever deal with NULL values in terms of Java methods. Well what about in ColdFusion; can I return a NULL value from a ColdFusion user defined function? And if so, does it work in the same way? To test this, I set up a simple ColdFusion user defined function which returns a NULL value using JavaCast():

	hint="Returns a NULL value.">

	<!--- Return a Java null. --->
	<cfreturn JavaCast( "null", 0 ) />

Now, I am gonna see what happens when I store that returned value into a ColdFusion struct:

<!--- Create a Data Struct. --->
<cfset objData = StructNew() />

<!--- Store NULL value. --->
<cfset objData.Null = GetNull() />

<!--- Test for KEY existence. --->
#StructKeyExists( objData, "Null" )#

Running the code above, we get the following output:


Cool. It looks like ColdFusion handles NULL values in exactly the same way whether it was returned from Java method or a ColdFusion user defined function. I am not sure if I would ever use this, but, I have to say that I do sort of like the way Java returns NULL values when it ends things like loop conditions. It might be worth looking into making that a ColdFusion standard as well.

Want to use code from this post? Check out the license.

Reader Comments


That's "null" btw, not NULL. Java is case sensitive and keywords are all lowercase.

The concept of null in Java is that it is 'nothing'. It's a primitive type that's only equal to itself (unlike SQL) and it's not something you can call methods on or use for much of anything but representing 'nothing'.

In CF however, null is really dangerous. You can't compare it to anything else, you can't pass it to CF functions, you can't assign it to some variables, and all kinds of other problems.

Pretty much all you can do with null in CF is get it to pass to Java methods or check if something is null using isDefined().

As for Java, java doesn't use null for loop ending. There's a method called hasNext() or hasMoreElements() or some such other iterator method that tells you if there is more. the next() or nextElement() methods return the next element. It's just a last resort to return null in the even there's no more left (most methods don't actually do this) and you call one of these methods, and even then that's not always true.

In fact methods like next() on the Iterator interface throw NoSuchElementException exceptions when you ask for another element and there's none left.

Did you mean something else for 'loop conditions' ?



Sorry, you are correct. I was not clear. I didn't mean "looping" in general. I meant just what you said - that some methods in Java return null when they run out of elements. Take for example the LineNumberReader. A some point, the call to ReadLine() will return null, which will then "delete" the variable into which it is stored; I then have to check for that key existence, etc. I use this most generally in a "looping" context.

So, when I said "looping" I meant that that is the situation in which this mostly comes up; I didn't mean to say that that is how Java performs loops in general. Sorry for the confusion.


You may know this - but I only discovered it a couple of weeks ago...

The same behavior (deleting the variable) is also exhibited iif you have the following within a cffunction:


The return type of the function needs to be "Any" (or "Void" - but it it was void, then there would be no need to check it)


Hi Ben!
I have a CF-Java codes (not written by me, I don't speak java) that converts a text feed into a query.
All I need to do is to query this query and use the resultset. Unfortunately this java things create difficulty on my simple query may be it is related to what you wrote in this blog about java returning null instead of empty string(?)

My simple query below threw this error:
query to query run time error:
Comparison exception while executing <>.
Unsupported Type Comparison Exception: The <> operator does not support comparison between the following types:
Left hand side expression type = "DOUBLE".
Right hand side expression type = "STRING".

<cfquery name="test" dbtype="query>
Select SSN, Birthdate from MyQuery
Where SSN <> '' OR
Birthdate <> ''



What you are running into is one of the many times that ColdFusion query of queries become frustrating. Probably, ColdFusion is either trying to convert SSN numbers OR Birthdays into a numberic value (DOUBLE) such that your string '' is not a valid comparison. Try casting the SSN and bday back to varchar:

<cfquery name="test" dbtype="query>
Select SSN, Birthdate from MyQuery
CAST( Birthdate AS VARCHAR ) <> ''


I was just looking for the same but in CFMX 6.1
Have you figured out to pass "null" to a Java Constructor or a Method? in CFMX 6.1



I haven't been on CFMX in a long time. It looks like javaCast() only added support for NULL values in CF7. Perhaps you can try calling a Java method that returns a NULL value (and pass that to the constructor). Sorry I don't have any better advice.

I believe in love. I believe in compassion. I believe in human rights. I believe that we can afford to give more of these gifts to the world around us because it costs us nothing to be decent and kind and understanding. And, I want you to know that when you land on this site, you are accepted for who you are, no matter how you identify, what truths you live, or whatever kind of goofy shit makes you feel alive! Rock on with your bad self!
Ben Nadel