If it's accepted as bug (or as javadoc bug) I can fix it. Gimme a hint. Georg
Georg Ragaller (JIRA) wrote: > [ > http://issues.ops4j.org/jira/browse/QI-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11406 > ] > > Georg Ragaller commented on QI-70: > ---------------------------------- > > IssueTest added in tests/auxillary/src/test/java/org/qi4j/tests/jira/qi70/ > >> @NotEmpty causes java.lang.NullPointerException >> ----------------------------------------------- >> >> Key: QI-70 >> URL: http://issues.ops4j.org/jira/browse/QI-70 >> Project: Qi4j >> Issue Type: Bug >> Reporter: Georg Ragaller >> Assignee: Rickard Öberg >> >> The javadoc of @NotEmpty states 'Marks a property as being a string, non >> null, non empty.'. >> But if a null value is checked a >> java.lang.NullPointerException >> at >> org.qi4j.library.framework.constraint.NotEmptyConstraint.isValid(NotEmptyConstraint.java:37) >> at >> org.qi4j.library.framework.constraint.NotEmptyConstraint.isValid(NotEmptyConstraint.java:1) >> at >> org.qi4j.runtime.composite.ConstraintInstance.isValid(ConstraintInstance.java:41) >> ... >> occures (Proj.Rev. 12020) > _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
