[
https://issues.apache.org/jira/browse/TAP5-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806739#action_12806739
]
Giulio Micali edited comment on TAP5-255 at 1/30/10 9:15 PM:
-------------------------------------------------------------
I agree, the clientID must be forceable(callers must ensure that the forced ID
is exactly the same previously used) in the zone class: I have done the same
recompiling the tapstry-core project, and....
with a Zone subclassing, now I'm able to provide FormSupport also in zones
which contains form fields.
I will attach the patch from my local copy, which contains also an override
capability for the "show" and "update" parameters (see TAP5-990)
P.S.
I included the "System.out.println" line in the patch just to explain the
point(and for my test purposes): if approved, the line should be removed.
was (Author: gmicali):
I agree, the clientID must be forceable(callers must ensure that the forced
ID is exactly the same previously used) in the zone class: I have done the same
recompiling the tapstry-core project, and....
with a Zone subclassing, now I'm able to provide FormSupport also in zones
which contains form fields.
I will attach the patch from my local copy, which contains also an override
capability for the "show" and "update" parameters (see TAP5-990)
> Easy management of zones inside a loop
> --------------------------------------
>
> Key: TAP5-255
> URL: https://issues.apache.org/jira/browse/TAP5-255
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Stéphane Decleire
> Attachments: select.diff, Test.java, Test.tml, zone.patch
>
>
> Enhancing the management of zones inside loops by removing the following zone
> limitation :
> "Unlike many other situations, Tapestry relies on you to specify useful and
> unique ids to Zone components, then reference those ids inside ActionLink
> components.
> Using Zone components inside any kind of loop may cause additional problems,
> as Tapestry will uniqueify the client id you specify (appending an index
> number)."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
