> One thing I mean by integration is a built-in loadable > detachable model for Hibernate mapped objects, like what's in > contrib.data and contrib.database.
Sorry, but if you want this feature in the ui layer then it is a tier argument as you should be doing this through a dao object. Wicket already provides a good generic wicket.model.LoadableDetachableModel that you can use to load entities from the database. All you need to do is override load and use your dao to bring the data in. I suggest you take a look at the wicket-phonebook example. > After that, you need an > easy way for people to fill up list views with query results. > If there weren't a use for base classes that help in these > tasks, the several contributed ones would not exist. The dataview package makes it trivial to create pageable/sortable list views of the database data, all you need is an iterator. Once again check out the wicket-phonebook example. -Igor ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
