I like for my entities to always be serializable. Is there some special requirement to have a non-serializable field on your entity class?
On Fri, Apr 18, 2008 at 4:50 PM, Fernando Wermus <[EMAIL PROTECTED]> wrote: > I am finishing my first app for production in wicket. As any newbie I try to > make a side relevant non-functional problems to focus in which I consider > important. > I was implementing Serializable in all my entities, but I have to change now > that. I ve done it using LoadableDetachableModel. But I couldn't do it in > some parts. When the user walks over a wizard to create an entity, I just > attached to the wizard a new entity and, finally I persist it in the las > step. But, I have to change that now, because the entity is not Serializable > anymore. > > Which is the best way? > > I think it is attaching a model which have all the attributes needed for the > creation of the entity and at the end I have to copy the whole information > to my entity, doesn' it? (like I was doing with j2ee DTO :( ). Then I have a > modelForm of the view and my entities at the end of the steps. > > Is there a best approach to it? > > Bye! > > ps: sorry for my english. > -- > Fernando Wermus. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
