Entity selected from the rich:dataTable with paging issue

Question

I tend to use rich:dataTable and retrieve entities clicked with this code.
     public final static Object selecionado(final String formulario,final String tabela) {
          try {
               final UIComponent comp = FacesContext.getCurrentInstance().getViewRoot().findComponent(formulario);
               final javax.faces.component.UIData data = (javax.faces.component.UIData) comp.findComponent(tabela);
               return data.getRowData();
          } catch (final Exception e) {
               throw new IllegalArgumentException("There was an error on select entity from table.\n" +
                         "Form = " +formulario+"\n" +"Tabela:" +tabela+"\n" +"Look up if the names are correct. <h:form id=\""
                         +formulario+"\"> e"+" <h:dataTable id=\""+tabela+">",e);
     }{code}
ps: I create a column of type h:commandlink and its call to action (which performs this method to see which entity was selected).
It works perfectly on the first page (rich:datascroller) but when I navigate to another page and click on the link (edit) the code is not even executed (I confirm this on debug mode too) and what happens is that the paging sends me back to page one.
Is there anything I can do?
Best regards,                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

Answer 1

I'm assuming you have <h:messages/> on your page?
The action events are queued during the Apply Request Values phase of the request. Typically if an action is not queued it is because some state of the components is not same as it was during the Render Response of the previous request. For example, if the value of the rendered attribute somehow changed, a component will not queue an action if it thinks it was not rendered.
It your case the most likely thing to have changed seems to be the pagination state of the dataTable. The table thinks it is on the first page for some reason during the Apply Request Values phase and so iterates over the data in the first page and never discovers the request flag indicating that an event should be fired for data in the second page. So the action event is not queued, nothing happens in the Execute Action phase and the Render Response phase simply re-renders the existing view.