Does the original exception not appear in the stack trace somewhere?
I don't know whether it is part of your question or not, but "org.hibernate.QueryException: could not resolve property" is usually related to a missing property on the EJB, either it has been mistyped in the JSF, or you are missing the getters/setters on the entity bean.
Thanks for the response. As far as I remember (at home now), there was absolutely nothing in the stack trace (jboss log/eclipse console). I think it's all related to this and the JSF spec's poor exception handling extensibility.
The exception was throw due to an incorrect parameter in the WHERE clause of my select query - rookie mistake :)
Thanks for your help Andy,
I thought I'd leave a note for anyone who has a similar problem in the future. It's the JSF RI's fault, as the above bug list shows.
Avoid initiating action logic in getters and setters - run time exceptions (and i assume app exceptions) will be lost (try it yourself, throw a runtimeexception in a getter.
Look into using a actions @factory and valuechangelisteners to initiate app logic, you may have more luck :)