There were no objections, we will go forward with the changes and include
deprecated code to support the old methods (with warnings).
I will create a JIRA issue to monitor this request.
-Andrew
On Jan 30, 2008 5:12 PM, Andrew Robinson [EMAIL PROTECTED]
wrote:
Just had some offline feedback,
yeah, I am in that boat as well.
clearer.
-Matthias
On Jan 31, 2008 11:37 PM, Jeanne Waldman [EMAIL PROTECTED] wrote:
I like this solution because it is much clearer to me. I would like to
know/investigate what someone would have to change in his jspx file
between this solution and the
+1 Looks good to me and I have been struggling to understand the existing
thing. Thanks,
Bruno
On 31/01/2008, Martin Marinschek [EMAIL PROTECTED] wrote:
+1 : yes I want this change
indeed, I find it a lot more logical like this.
regards,
Martin
+1 , use string arrays to use multiple partial triggers makes that the logic
of the page be in 2 places, so this solution is good
I like this solution because it is much clearer to me. I would like to
know/investigate what someone would have to change in his jspx file
between this solution and the original solution (before the bug was fixed).
Is it only if the partialTriggers were on a naming container and it is
looking
f:subview id=A
tr:commandButton id=B /
tr:table id=C partialTriggers=::B E G ::H:I:K ::H:N
tr:column id=D
tr:commandButton id=E /
tr:inputText partialTriggers=::B E G ::C ::H:I:K ::H:N /
/tr:column
tr:column id=F
tr:commandButton id=G /
/tr:column
+1 : yes I want this change
indeed, I find it a lot more logical like this.
regards,
Martin
