Yesterday I was writing what I thought to be some pretty simple HQL:

var res = ormExecuteQuery("from user where email = :email", {});

Unfortunately I kept getting the Java Lazy Cop Out error (sorry, I mean the Null Pointer Error):

java.lang.NullPointerException at org.hibernate.param.NamedParameterSpecification.bind( at org.hibernate.loader.hql.QueryLoader.bindParameterValues( at org.hibernate.loader.Loader.prepareQueryStatement( at org.hibernate.loader.Loader.doQuery( at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections( at you get the idea.

The error seemed to imply something wrong with my named parameter, email. I did a dump on the arguments scope to ensure email existed and it did. So what was it? Turns out I had not defined email as a property of my entity! Surely the error could have recognized that. Once I actually added email (and ran an ormReload - don't forget ColdFusion caches such definitions), it worked. I tweeted this last night and Joe Rinehart pointed you get the same issue if your case in the HQL statement does not match the case defined in your entity. That's correct too. Changing my code like so:

var res = ormExecuteQuery("from user where eMail = :email", {});

Also threw an NPE as well. sigh So - is this a ColdFusion or Hibernate bug? I'm not sure. If this is how Hibernate throws the error, than ColdFusion can't do much about it. I'm filing a bug anyway just to be sure. I know that Adobe did a lot of work in ColdFusion 9.0.1 to improve the error messages from ORM issues so if this can be updated as well, it would help.