Improve the error message when using a paged version of EntityQuery without defining the
maxResults property
------------------------------------------------------------------------------------------------------------
Key: JBSEAM-2747
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2747
Project: JBoss Seam
Issue Type: Feature Request
Reporter: Fernando Montaño
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