Max,
I managed to use our own collectionmodel with a solution similar to what
you suggested (have a method in my backing bean itself wrap the list).
It was a bit complicated because we are using nested tables, so we
always have to keep track of the parent table. But in fact that was
Hi,
I found one way to force the trinidad table to use our own collection
model: to extend
org.apache.myfaces.trinidad.component.core.data.CoreTable and override
the createCollectionModel method. But I don't like this solution
because for this to work I have to make this method non-final in
Henk,
I must be missing something - why don't you just instantiate your custom
CollectionModel as a backing bean
and EL-bind table's value to it?
Max
Henk Vanhoe wrote:
Hi,
I found one way to force the trinidad table to use our own collection
model: to extend
Hi Max,
I cannot use my custom model in the backing bean because it is an EJB3
entity with a one-to-many relationship to another entity. The table
should be filled with instances of this other entity but they are only
available in the first entity as a java.util.List. This List is filled
by
Henk,
How about having a simple backing bean used as a table value (for
example - value={#mybean.collectionModel}.
You can execute EL in getCollectionModel() implementation of mybean to
get the java.util.List, then return an instance
of your custom collection model that wraps the List.
Max
5 matches
Mail list logo
