-
15. Re: Which component for a sortable list?
I'm still very confused, that Richfaces offers no possibility to sort a datatable. As already said, the scrollable datatable is full of bugs and very overloaded.
Trinidad has antother drawback as it's not support the JBoss Seam Method invocation trough EL.
Pete, was Is my benefit if I use a entityQuery? I think I still need the overloaded Trinidad-Table, or not?
Are there no other solutions for this Problem? Do I need to look for a comercial component library?
Daniel
-
16. Re: Which component for a sortable list?
I too would like to know the problem with the sortable table and paginator with ICEfaces since we have created several applications using these components. What do you mean by 2 screens with datatables...is this the same datatable on 2 separate pages? This shouldn't be a problem...You would have to be pretty careful with the scope of the backing bean though and the manipuation of the conversation, but it shouldn't be a problem. If you attach a simple example of this problem to ICEfaces Seam integration forum we can take a look at it.
-
17. Re: Which component for a sortable list?
You've mentioned the scrollable data table form richfaces specifically, now-a-days the normal data table is also sortable.
Might be worth a look.
-
18. Re: Which component for a sortable list?
Personally, I'm still using Tomahawk. Its sortable header is dead simple, and allows for delegation (unlike RichFaces, which insists on sorting the data model by itself). It's very useful for large paged datasets backed by an EntityQuery - whenever a user requests sorting, the backing bean simply constructs the JPA sort clause and passes it to the query, refreshing it.