Interesting idea - I could go for that... Not 100% thrilled about
adding a new EL variable, but OTOH I could also question why we'd
ever want varStatus set to the selected row (which happens if you
tie currency to selection).

-- Adam
On 10/23/07, max.starets wrote:

Good point, Adam.

I submitted a new patch for JIRA-771 that completely reverts changes made
for JIRA-737.

Regarding concerns raised in JIRA-737: would it make sense to provide an EL
for selected row (add a "selectedVar" property for table)? This would allow
code to refer to the selected row (which I always thought was lacking in
table) without
us having to do something ugly with the client IDs.


Adam Winer wrote:
On 10/17/07, max.starets wrote:

Thanks, Adam.

I like your suggestion. The only exception I see is that we would still
establish currency for selection events. Agreed?
Wouldn't that still mean that if you launch a dialog during a selection
event, the return will fail?. Or that PPR'ing a facet of the table in
to a selection event will likely fail?

I'm wondering if we want something much uglier here: a way to
still establish currency (and do it for all events), but without
mucking with client IDs.

-- Adam
View this message in context: http://www.nabble.com/-Trinidad-1.0.3--returnListener-is-broken-tf4594019.html#a13365888
Sent from the MyFaces - Users mailing list archive at Nabble.com.

Search Discussions

Discussion Posts


Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 8 of 8 | next ›
Discussion Overview
groupusers @
postedOct 9, '07 at 12:49p
activeOct 23, '07 at 8:13p



site design / logo © 2019 Grokbase