I debugged into some methods of UIData and after that I'm wondering how the DataModel ever knew which row had been selected.
It seems that the rowIndex ist set to -1 at the very beginning and the very end of the "Apply Request Values", "Process Validations" and "Process Updates" phases. processDecodes, processValidations and processUpdates of UIData call setRowIndex(-1) twice. So for me the only point where the DataTable saves the selected index seems to be the "Invoke Application" phase. I debugged into broadcast of UIData and only when it's calles in this phase, the eventRowIndex is assigned the real selected index. This index is saved in the DataTable via setRowIndex(eventRowIndex). currentRowIndex gets the index before, which is -1. But then it happens. A further method is called in a try-finally-block. The finally-part calls setRowIndex(currentRowIndex), where currentRowIndex is -1. That's confusing. Before the "Invoke Application" phase the index is continously set to -1. So it can't have another value until the "Invoke Application" phase begins. Then it is set to the real selected index. 7 lines later it is reset to -1. Where is the dataTable opposed to get its selected index? I'm convinced I overlooked sth. but what? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3934657#3934657 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3934657 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
