0 Replies Latest reply on Jun 2, 2010 4:17 AM by devora

    a4j:support problem - AjaxUpdate component not found for id

    devora

      Hi!

       

      I have a rich:dataTable on my screen. It's supported with an a4j:support tag.

      It looks like this:

       

       

      <rich:dataTable
      value="#{manageUsersBean.usersRoles}" id="details" var="user"
      rowKeyVar="index" border="1" rows="8" width="100%">
      <f:facet name="header">
      <rich:columnGroup>
       
      <rich:column>
      <h:outputText value="User name " />
      </rich:column>
       
      <rich:column>
      <h:outputText value="password" />
      </rich:column>
      </rich:columnGroup>
      </f:facet>
      <rich:columnGroup>
      <rich:column>
      <h:outputText value="#{user.user.name}" styleClass="schColL"/>
      </rich:column>
      <rich:column>
      <h:outputText value="#{user.user.password}" styleClass="schColL"/>
      </rich:column>
      </rich:columnGroup>
       
      <f:facet name="footer">
      <rich:datascroller id="details" renderIfSinglePage="false"></rich:datascroller>
      </f:facet>
      <a4j:support actionListener="#{manageUsersBean.getRoles}" id="click"
      event="onRowClick" 
      reRender="details,roles">
      <f:param value="#{user.user.id}"
      name="rolesUserId" />
      </a4j:support> 
      </rich:dataTable>
      
      
      

      It worked nicely till we upgraded the project the JSF2 with richfaces 3.3.3. now it throws me an exception:

       

       

      javax.serv
      let.ServletException: AjaxUpdate component not found for id: click
           javax.faces.webapp.FacesServlet.service(FacesServlet.java:325)
           org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206)
           org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
           org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
      ..........
      
      

       

       

      Can you tell me what it has to do what could it be.

       

      Another thing: When I remove the rich:columnGroup tag, with it's content, the exception is nor being thrown, and it works ok. (Again, the columnGroup was working before!)