From what I understand, the add attribute of the grid element is here
just to do that : add placeholder column, typically to put some actions
on the content of the row (like editing, detailing, deleting etc...).
I created the following JIRA :
Key: TAPESTRY-2451
It would be nice if we were able to add a not existent property to
Grid and BeanEditForm without having to declare the model explicitly
in the class... that's what i thought the first time i saw the "add"
parameter in these components, but it just works this way inside the
class.
José, did you fir
You're welcome, glad it helped.
And now I know why I didn't see this message on the mailing list: The T5
in the subject was missing.
zack1403 schrieb:
On #tapestry, TobiasW suggested to add the columns through beanmodel instead
of in my tml which turned out to work just fine. Definitely look
On #tapestry, TobiasW suggested to add the columns through beanmodel instead
of in my tml which turned out to work just fine. Definitely looks like a
bug to me. My bean model code might help anyone else with this issue and
doesnt know how to do it from the page class:
@Inject
private ComponentR
My grid is not in a form fragment, so I would say no, but I'm not sure.
I really dont see why the volatile=true attribute could fix that.
Anyway, I'm openning a JIRA on this. It smells like a sneaky bug.
José
zack1403 a écrit :
On #tapestry, y informed me to try volatile="true", but this didnt
On #tapestry, y informed me to try volatile="true", but this didnt fix the
issue for me. Jose, maybe that might work for you?
Does it matter that my grid is within a formfragment?
Zack
zack1403 wrote:
>
> Anyone have any ideas on this? I am stuck on this exact same issue and
> have not been
Anyone have any ideas on this? I am stuck on this exact same issue and have
not been able to find a workaround.
Zack
José Paumard wrote:
>
> Hello all,
>
> I put a grid in a form, and added a column in that grid, to hold special
> options about the item on the given row.
>
> I wrote somethi
