[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

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.1.0.GA, 2.0.2.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.