We use p:datatable within our own composite component. Also the p:columns are wrapped in our own component. It is not possible to set the "sortBy" attribute of p:column with a value expression. Internally the DataHelper class just removes #{} and the table variable from the expression string. The expression itself is not evaluated.

Here´s a possible solution for that problem that works perfect for us:

String resolveField(ValueExpression expression) { Object newValue = expression.getValue(FacesContext.getCurrentInstance().getELContext());

if (newValue == null || !(newValue instanceof String))
    return resolveField_old (expression);
else {
    String val = (String)newValue;
    return val.substring(val.indexOf(".") + 1);
}

}

String resolveField_old(ValueExpression expression) { String expressionString = expression.getExpressionString(); expressionString = expressionString.substring(2, expressionString.length() - 1); //Remove #{}

return expressionString.substring(expressionString.indexOf(".") + 1);                //Remove var
}

This feature is really important for us.

What steps will reproduce the problem? 1. sortBy="#{item.firstname}" works because the logic extracts "firstname" 2. sortBy="#{column.sortByExpression}" doesn´t work because the expression is not evaluated

What is the PrimeFaces version? 2.2.1

What is the expected output? What do you see instead? I expect that the sortBy expression is evaluated

Which JSF implementation with version are you using?(Mojarra or MyFaces) Mojarra

Which component libraries are you using in addition to PrimeFaces? None

Which application server or servlet container are you using? Glassfish 3.1

This bug describes a similar problem with the DataHelper class.

http://code.google.com/p/primefaces/issues/detail?id=2349

Multiple selection doesn´t work because of wrong (missing) expression evaluation.

Issue 2349 has been merged into this issue.

Review for RC1.

Comment deleted