Yes, Tapestry tries very hard to work however people feel comfortable..
With 4.1.2 especially I don't understand why
wouldn't work with a updateComponents="updateArea" parameter value. The
client id logic / unique loop id generation / etc should all be handled
transparently but maybe
cool, I was completely wrong then - didn't know, it worked with client-side
id's. Something like that would really be a nice example for the docs, I
think!
2007/7/6, Malin Ljungh <[EMAIL PROTECTED]>:
Well, actually I works excellent!
I have it like this in my template now:
...
Well, actually I works excellent!
I have it like this in my template now:
...
(loopContacts is of type For)
and on every row I have edit button which swithes current contact from
display to edit form.
So on edit linkbutton I have this:
and the same on submit/save button.
Yes, you should be able to define any attribute (=informal parameter) in the
template, in the spec or in annotated Java. In some components, however, id
is a reserved parameter, because the component insists on generating it
itself.
But I think even if you had your data-id in the client-side elem
OK, it does NOT work to have the ognl id in the page-file.
Not that it's important - but ... am I correct?
I thought everything could be done either way.
On 7/6/07, Malin Ljungh <[EMAIL PROTECTED]> wrote:
Andreas!
That was EXACTLY what I was looking for!!! Thanks!!!
(And thank you Marcus too
Andreas!
That was EXACTLY what I was looking for!!! Thanks!!!
(And thank you Marcus too, I'll to refresh the whole loop if this doesn't
work out)
Actually I started with something like this but I normally use just jwcid in
my .html file and have everything else in the page-specification (.page
f
But he can set the id parameter to whatever he likes, i.e.
data
On 7/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
As there are no dynamic component instances in Tapestry, there are no
dynamic component-ids. What you are seeing (loopContacts_i, i=1 ...) are
multiple clientId's (Element id'
As there are no dynamic component instances in Tapestry, there are no
dynamic component-ids. What you are seeing (loopContacts_i, i=1 ...) are
multiple clientId's (Element id's on the client side) rendere by one and
the same component instance, whose id, the component-id on the server,
is "loopCont
