If you put onException AFTER the route definition, the build compiles with no problem, but the exception does get triggered. The work-around for now is to make sure that all onExceptions are specified PRIOR to route definition. This should be fixed to allow for onException after the routes or at least throw some sort of error saying that this is not allowed - not sure which solution is best yet.