[hibernate-issues] [Hibernate-JIRA] Created: (HBX-903) Better error-handling when executing jpql/hql statements

[Joseph Marques (JIRA)]

Better error-handling when executing jpql/hql statements
--------------------------------------------------------

         Key: HBX-903
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-903
     Project: Hibernate Tools
        Type: New Feature

    Versions: 3.2beta8    
    Reporter: Joseph Marques


i was written a query that used composite objects, such as:

select new Thing(elt1, elt2) from .....

and the class Thing had the following toString implementation:

public class Thing {
   ...
   public Stirng toString() {
      return elt1.toString + ", " + elt2.toString();
   }
   ...
}

Most of the time elt2 has a valid value, but occassionally the model will return a valid result where elt2 is null.  Obviously, this is going to make the toString implementation bomb with a NullPointerException - but I received one error for EVERY SINGLE RESULT ITEM that has null in it.  So, when I was querying several hundred objects, I basically just sat on the return key (to accept the error msg boxes that popped up) until several dozen of them were acknowledged.

I think it would be more intuitive to aggregate the exceptions by thrown location and type, and then insert into the error log something like "Problems occured when invoking code from plug-in: 'org.eclipse.jface' (56 times)" and then only notify me with a single pop-up error msg box - instead of 56 errors in the log and 56 modal msg boxes that I have to accept before I can continue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira