anonymous wrote : First of all the data model seems to be some collection, maybe seam could provide a model which can rely on paging as well, thus not the entire collection has to be loaded. (some kind of ejb3 jsf data model)
There is no problem here, pagination is easy to implement (the Hibernate Tools plugin actually generates code to do pagination). All you do is have a nextPage() action that re-runs the query with a diff setFirstResults()/setMaxResults(). Very, very simple. anonymous wrote : Another thing is, you have a model counter, which is a cood thing, which can be automatically requested, after an action from the data table itself. But this is a problematic pattern, because data can change in between, thus passing the surrogate of the affected object or the object makes more sense in this case. Huh?? I think you have misunderstood. This is a *stateful* session bean. The list is cached. anonymous wrote : Third, setup, programming and deployment. This is somewhat the biggest problem. Yes, this can be a bit tricky. For now, the best way is "follow the examples". Another way is to use Hibernate Tools to generate everything. anonymous wrote : Some of the config files need documentation I have tried to do this. Which files in particular are lacking? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3913351#3913351 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3913351 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
