Throwing better exceptions with Lucee 6 with cause

[Zackster]

One of my favourite little additions with Lucee 6 is being able to pass an exception into a custom throw statement.

For example, if you are doing something in a try catch block, I find myself often wanting to add some additional context to the exception, to be kind to my future self.

The new <CFTHROW> / throw() cause attribute let’s you do this, adding the initial caught exception to the Caused By: section at the bottom of the stack trace.

<cfscript>
	userId=123;
	try {
		// do some stuff which might fail
		throw( message="database constraint violation" );
	} catch ( any e ) {
		// add some useful context to the exception
		throw( message="Error Migrating user [#userId#]", cause=e );
	}
</cfscript>

…

cfthrow :: Lucee Documentation

Exception - Cause :: Lucee Documentation

Lucee 6, nested exceptions

Lucee has 6 has a great new feature, being able to add a cause to an exception [LDEV-438] - Lucee What does this mean? You can catch an error and then throw another error and add the original exception into the new error i.e. something like a database error blows up, you can then throw a nice error saying duplicate user and then include the original exception an example and how to do this in older lucee versions TryCF.com PS: just on the caused by section in java stacktraces, they are often …