Sorry I was trying to explain my situation better but made it worse. Here is my
scenario. The person.xhtml page shows all the properties of Person entity. In
this page, I need to show top 5 records of person's calls and reviews. Here is
the code:
| <h:outputText value="#{person.name}" />
| <h:outputText value="#{person.age}" />
| <h:dataTable value="#{person.reviews}" var="review" >
| <h:outputText value="#{review.title}" />
| </h:dataTable>
|
| <h:dataTable value="#{person.calls}" var="call" >
| <h:outputText value="#{call.duration}" />
| </h:dataTable>
|
Paginating for {person} is easy when using Query. but to paginating for
{person.reviews} and {person.calls} is not easy. By now, I have to create a
pagination object for each collection based property. If Person has 4
collection type properties (e.g. calls,reviews...), I basically have to create
4 extra pagination objects with customised Hsqls for pagination. It's so time
consuming to do it this way. If I use t:dataScroller, I wouldn't have to create
those 4 extra objects. But as you said, there's performance problem with
t:dataScroller. It would be nice if Seam can provide a s:dataScroller, which
support real database based pagination.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006893#4006893
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006893
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
