Hello, What do you make of the following ? A "view model" associated with each view (mostly for edit forms). This model (separate from LDMs encapsulating entities) would handle all FormComponent values and updates (select lists, etc..). At creation it would extract required entity properties and upon submit would be called to hydrate the entity with the changes and save. Up until recently I put most of this logic in the Panels alongside the actual components and the idea of calling services for saving entities from an IModel seems wrong somehow but I would be interested in your take on this ...
Thanks! CN -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/patterns-for-web-ui-apps-mvc-models-tp1867567p4677441.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
