[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2747) nextExists on EntityQuery throws exception when maxResults is not set

Norman Richards (JIRA) jira-events at lists.jboss.org
Wed Mar 26 15:01:40 EDT 2008


     [ http://jira.jboss.com/jira/browse/JBSEAM-2747?page=all ]

Norman Richards closed JBSEAM-2747.
-----------------------------------

    Resolution: Done

Changed issue name to more accurately reflect the problem.  Null pointer is no longer generated.




> nextExists on EntityQuery throws exception when maxResults is not set
> ---------------------------------------------------------------------
>
>                 Key: JBSEAM-2747
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2747
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 2.1.0.A1, 2.0.1.GA
>            Reporter: Fernando Montaño
>         Assigned To: Norman Richards
>             Fix For: 2.0.2.GA, 2.1.0.GA
>
>
> When someone tries to use a paged version of EntityQuery (e.g. invoking isNextExists() from xhtml) without defining a value for the maxResults property, one gets a NullPointerException. It would be better to have a nicest error message instead a NPE.

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

       




More information about the seam-issues mailing list