Customer has just reported the following:

BEGIN: The problem appears to lie in following:

In the datatable the

<ice:column>
<ice:outputResource>

combination appears to show in OutputResourceRenderer

String clientId = uiComponent.getClientId(facesContext);
OutputResource outputResource = (OutputResource) uiComponent;

shows the uiComponent being the same each time the renderer is called, with clientId different on each row. The uiComponent is not safe to use as a singleton since

public Resource getResource() {
ValueBinding vb = getValueBinding("resource");
resource = (Resource) vb.getValue(getFacesContext());

Where resource is a private member which is then used later in the code in the within Resource r = new Resource() {

To work around the issue until you can resolve it, I have introducted some code enclosed which appears to resolve issue. See internalResource variable.. It is probably now the most optimal way to resolve issue but it works..

END

OutputResource.war

OutputResource.java

I'm not sure if this is the root of problem, but I had changed the getResource() method on the component to actually first check the value binding and set the instance variable off of that to avoid this issue:

http://jira.icefaces.org/browse/ICE-2348#action_22973

public Resource getResource() {
ValueBinding vb = getValueBinding("resource");
resource = (Resource) vb.getValue(getFacesContext());
...

After debugging the code I found out that the problem is due to the reason that "clicking" on the "resource" link, works as request/response mechanism and it doesn't involve JSF Life cycle at all. So the dataTable does not have chance to load the proper row object into the scope.

The OuputResource component uses inner class to define the resource, so to responds the request the ResourceDispatcher invokes the "open" method on the "resource", which uses the reference of the most recently evaluated "resource" object by the outputResource component. That is why every link inside the table brings the same resource and that obviously for the last row of the dataTable.

I couldn't see any straight fix to the component, it might require something to change with Resource API as well. So I am re-assigning it to Mircea.

trunk revision : 17820

Even though there is a single instance of the outputResource component when inside the dataTable, but there are designated resource objects for each resource, that allowed to fix this issue at the component level. The fix is to not to update the reference of instance member of its parent class, use the value binding instead.

Branch 1.7 : revision 17830