Another Question on Stateless pagination

[chadws]

I have been reading a lot more in the documentation and on various blogs and have run across a post by Gavin King

Pagination in Hibernate and EJB3

and a couple of follow-up posts on another blog:

User Friendly Paging with Seam

Seam Page Parameter with cutom Validators and Converters

I guess I am confused about how all of this ties together: the statefull vs stateless conversations. Using this pattern I was able to create a listing of a given object using a stateless session bean and the Page object from Gavin's post. However, I am unable to use the s:link tag in my datatable and pass in the object the user clicks on as a argument to my action method, I am assuming this is due to there being no state to restore the view and so the object is unknown?

Having stated this what method is reccommended for moving from a stateless listing of items to a stateful conversation   in seam?

Do most people pass in the id of the object to be edited / viewed and then use another stateless bean to load the entity for viewing?

[damianharvey.damianharvey.gmail.com]

You need to annotate the list that drives the dataTable with @DataModel if you wish to pass the current row as an argument of a method.

Passing the ID of the object is more RESTful which has a lot of benefits (logical URLs, linkability, etc). I've done all of mine using @DataModel but at some stage I plan to go back and redo most of it with IDs (again).

Cheers,

Damian.

[chadws]

Do you have an example of how you are using datamodel to handle this? I have tried, but each time my objects that are submitted are null and are not being retrieved properly?

[pmuir]

Read this