I've got those before as well, and that was the problem. Perhaps Tapestry could handle that better and just select the first item in this case?
Norman Franke Answering Service for Directors, Inc. www.myasd.com On Jul 10, 2012, at 8:11 AM, Thiago H de Paula Figueiredo wrote: > On Tue, 10 Jul 2012 08:54:25 -0300, Jabbar <aja...@gmail.com> wrote: > >> I think I found the problem, although I'm not 100% sure. I deleted the data >> which populated the selected property of the palette component and then >> added the data back into the database. The problem has disappeared. > > NPEs in Palette happen when one of the selected options is not present in the > model you passed to it. And, by "present", it means for each selected object, > selected.equals(option) return true for at least one of the options in the > model. > > -- > Thiago H. de Paula Figueiredo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org >
