Can't figure out simple method call per row of table

[dkarr]

JSF 1.1, RichFaces 3.1.3, WebLogic 9.2.2.

I'm trying to figure out something that should be simple. I have a datatable, and each row has a link to perform an action relative to the clicked row. Somehow, the action method needs to know what row the action was relative to.

The top of my datatable looks like this:

<rich:dataTable id="projectsTable" value="#{projectManager.projects}" title="Projects" var="project" columns="2" frame="border" rules="all" rowKeyVar="rowNum">

The column that defines the row-relative link is:

<rich:column>
 <f:facet name="header"><h:outputText value="Add"/></f:facet>
 <a4j:commandLink action="#{projectManager.addProject}" reRender="projectsTable" value="Add">
 <f:param name="rowNum" value="#{rowNum}"/>
 </a4j:commandLink>
</rich:column>

When I click the link, I see lots of debug on the console showing the data populated in the table, but it never calls my action method.

If it matters, my action method is just this:

public void addProject()
 {
 String rowNumStr =
 (String) FacesContext.getCurrentInstance().getExternalContext().
 getRequestParameterMap().get("rowNum");
 int rowNum = Integer.parseInt(rowNumStr);
 getProjects().add(rowNum, new ProjectBean());
 }

Any suggestions?

[steven.whatmore]

I am not 100% sure about this but we are doing something very similar, and this works for us.

Is the a4j:commandlink in the context of a form object (i.e surround your entire table with a a4j:form)?

Hope this helps.

Whatty

[dkarr]

I was about to send a quick response to the effect of "sure, I'm not that dumb", when I realized that I'm wrapping it with a "h:form", not a "a4j:form". Once I changed it to the latter, it worked perfectly.

You'd think there would be some runtime validation (optional, perhaps) to confirm the correct components are being used.

[steven.whatmore]

Actually we have been bit by that several times in various combinations of components where it was not properly enclosed in the required parent component.

A design time validator would sure be a nice addition, providing some form of warning when the correct components are not being used.