Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.1.6
-
None
-
None
-
Any
Description
The documentation does not impose any restriction on the value passed to forceIdIndexFormula. But as Tomahawk makes the value returned part of the component id, the value must confirm to the restrictions on component ids imposed by the specification. This should either be specified in the documentation (bad) or the value should be encoded when used in the component id (better).
The problem showed up in my case because the rows displayed show data from an LDAP server and the distinguished name used as unique key contains commas. This breaks Sun's JSF RI because it creates a JavaScript function invocation with "f(id,value)". When the id contains a comma (as in my case) the function arguments cannot be seperated properly any more.