Re: non-serializable objects to feed a DropDownChoice
Hi, Is there a problem in using LoadableDetachableModel> for the DropDownChoice ? Use this constuctor: public DropDownChoice(String id, IModel model, IModel> choices, IChoiceRenderer renderer) On Wed, Aug 28, 2019 at 10:56 PM René Stolle wrote: > Hello there, > > my domain classes are mostly not serializable. Making use of > LoadableDetachableModels I have no problems execpt of one situtation: I > couldn't find an easy solution to place a list of domain objects in a > DropDownChoice without getting serialization issues. The examples I > found ignore this problem and I have only a pretty complicated work > around. My domain classes have an id of type long (serializeable), which > I use in my solution. This works, but the code confuses me everytime I > have to touch it. > > My question now, how is this done the "wicket way" ? Is there an elegant > solution out there? > > René > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: non-serializable objects to feed a DropDownChoice
Why don't you use a pojo that could be a simplified view of your domain class (dto) ? François > Le 28 août 2019 à 20:49, René Stolle a écrit : > > Hello there, > > my domain classes are mostly not serializable. Making use of > LoadableDetachableModels I have no problems execpt of one situtation: I > couldn't find an easy solution to place a list of domain objects in a > DropDownChoice without getting serialization issues. The examples I found > ignore this problem and I have only a pretty complicated work around. My > domain classes have an id of type long (serializeable), which I use in my > solution. This works, but the code confuses me everytime I have to touch it. > > My question now, how is this done the "wicket way" ? Is there an elegant > solution out there? > > René > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
non-serializable objects to feed a DropDownChoice
Hello there, my domain classes are mostly not serializable. Making use of LoadableDetachableModels I have no problems execpt of one situtation: I couldn't find an easy solution to place a list of domain objects in a DropDownChoice without getting serialization issues. The examples I found ignore this problem and I have only a pretty complicated work around. My domain classes have an id of type long (serializeable), which I use in my solution. This works, but the code confuses me everytime I have to touch it. My question now, how is this done the "wicket way" ? Is there an elegant solution out there? René - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org