OK norman, thanx for your answer, I will try it may be for the next release
of seam, you can include more comple sample about paging, and don't forget to
make beter integration between seam and portal, where is gavin I am not saw his
post, for this last few days :)
Best Regards,
-haric-
I sent U zip file with IceFaces code...of my light paginator.
anonymous wrote :
| sherkan do you work with portlet also?
No i'm not.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3998207#3998207
Reply to the post :
You can use hibernate paging function
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3997888#3997888
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3997888
___
jboss-user mailing
is there any example about hibernate data paging? I think tomahawk data
scroller is cool and easy to use, but I don't know why, if I test only with
400.00 data it is very slow, because it actualy load all the data to the
memory, not load data on demand
View the original post :
Several of the seam examples (hotel booking, dvdstore, etc...) use it, as does
any application created by seam-gen.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3997928#3997928
Reply to the post :
Norman wrote
anonymous wrote :
| Several of the seam examples (hotel booking, dvdstore, etc...) use it, as
does any application created by seam-gen.
|
Norman, I have seen the example, but in that example there is no jum to n page
like we use tomahawk, maybe I can do it programmaticaly,
sherkan777 wrote :
anonymous wrote :
| This stuff has much bugs and changed then instead of IceFaces, here is
better dataPAginator nad full ajax force!
|
sherkan do you work with portlet also? I have tried Icefaces also, but found so
many errors, so I fallback to tomahawk, can you give
Sure - on EntityQuerym, use the firstResult attribute. To go to page N, set
firstResult to N*maxResults+1. You set it with f:param on the link. seam-gen
apps use this for first/last/next/prev pages, but there is no reason you can't
render page 1, page 2, etc... We don't have built in
