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 <[EMAIL PROTECTED]> 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 > variable > for selected row (add a "selectedVar" property for table)? This would allow > declarative > 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. > > Thanks, > Max > > > Adam Winer wrote: > > > > On 10/17/07, max.starets <[EMAIL PROTECTED]> 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 > > response > > 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. > >
