I am not sure what that is supposed to look like to the user.
However, your outputText element with ID "attributeTextdescription" has no value, so it's not going to display anything. I'm not sure, in fact that it will even generate the <span> element that is used to hold the CSS info for the outputText. So I'd recommend putting in a value="" attribute as a placeholder.
One thing that can help a lot when debugging JavaScript in a
JSF page is if you take complex javascript and wrap it in a javascript function. For quick-and-dirty function definitions, you can put them in a construct like this:
The verbatim tags permit JSF to pass through their body unmodified. The CDATA ensures that the XML parser won't get confused if "magic" xml characters such as ">" or "'" appear in the javascript expressions.
That results in the much simpler column definition:
When you do this, you can set breakpoints and use your javascript debugger to see what's happening. Note that I got rid of the raw HTML <a> tag, since the onclick works just as well on the outputText element.
I think, actually that your problem is that you didn't put quotes around #{currentAttribute.name} in your element value assignment, which would generate code expecting #{currentAttribute.name} to be the name of a javascript variable instead of a literal value like you wanted. But the trick I just described will make it easier to debug.