I haven't read through this thread very carefully, but last week I got a nearly identical stack trace. It was from Palette, not Select, but those components have a lot of identical code. In my case the problem was that the SelectModel had all of the expected values *except* the selected value. Tapestry didn't do a good job with the error messages in that case.
On Fri, Jul 11, 2014 at 5:36 AM, squallmat . <squall...@gmail.com> wrote: > When I do this : > > selectType = selectModelFactory.create(typeClientList, "nomType"); > selectApplications = selectModelFactory.create(applicatifList, "nom"); > > each lists (typeClientList and applicatifList) are not empty. > > And for the second parameter, I put the variable name of a String of an > object contained in the list, is this what have to be done ? > > > > > > 2014-07-10 16:57 GMT+02:00 Thiago H de Paula Figueiredo <thiag...@gmail.com> > : > >> On Thu, 10 Jul 2014 09:51:08 -0300, squallmat . <squall...@gmail.com> >> wrote: >> >> Caused by: java.lang.NullPointerException >>> at >>> org.apache.tapestry5.internal.util.SelectModelRenderer. >>> option(SelectModelRenderer.java:51) >>> >> >> Check whether you passed a null OptionModel to the SelectionModel. >> >> -- >> Thiago H. de Paula Figueiredo >> Tapestry, Java and Hibernate consultant and developer >> http://machina.com.br >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
