[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2747) Improve the error message when using a paged version of EntityQuery without defining a value for the maxResults property
[ http://jira.jboss.com/jira/browse/JBSEAM-2747?page=all ]
Pete Muir updated JBSEAM-2747:
------------------------------
Issue Type: Bug (was: Feature Request)
Component/s: Framework
Fix Version/s: 2.0.2.GA
2.1.0.GA
Affects Version/s: 2.1.0.A1
2.0.1.GA
Improve the error message when using a paged version of EntityQuery
without defining a value for the maxResults property
------------------------------------------------------------------------------------------------------------------------
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
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