Simon,
But still don't you think that it would be nice to include a value attribute
as part of panelGrid and let that value reference a panelGrid instance.  It
can be similar to what <t:navigationMenuItem> offers as value.  This is
pretty nice in cases where you don't want to maintain updating the model
object as you may do in the case of a binding but you just want to create
the object and associate it to a panelGrid just once...Anyway, my problem
continues,  what I am requiring is to be able to include a "code-generated"
table as a column in a datatable.  This table has to be only a row in size
but with a variable number of columns depending of each row´s specific
conditions.  Some rows may have some consecutive images, or a combination of
images and texts, or commandLinks, etc.  I tried using a binding but all my
rows get the same value which is the same as the first row.  I was thinking
of doing it with datatable but haven't came out with a clean solution since
the column types shouldn't be known at the xhtml page, there should be just
a mapping to a value on the bean and that value brings the whole datatable
object.  I don´t know if this is enough to make my point clear, the
requirement is probably toooooooooo specialized but that's software
engineering, the technology is the media and the sole ruler is the customer.

Regards and thanks,
JV  

-----Mensaje original-----
De: Simon Kitching [mailto:[EMAIL PROTECTED] 
Enviado el: miércoles, 08 de noviembre de 2006 20:57
Para: MyFaces Discussion
Asunto: Re: Appending dynamic table as column to datatable...

Jorge Vásquez wrote:
>
> I have another question, why doesn´t panelGrid have a value 
> attribute?  I think that it would be ideal for these kinds of 
> situations where you want to map many panelgrids to different 
> instances of HTmlPanelGrid, and probably embed them inside another 
> container.
>
>  
>

All "value bindings" on components ("value" is the most common name for 
such an attribute) reference a *model* object, not a component.

In the case of an h:dataTable for example the "value" attribute refers 
to a list of model objects to be rendered within the table, not a list 
of child components of the table.

An h:panelGrid may have child components, but it has no meaningful 
*model* object to refer to, so there is no "value" attribute on that 
component.

Regards,

Simon

Reply via email to