You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Michael Lipp (JIRA)" <de...@myfaces.apache.org> on 2006/08/29 09:57:23 UTC

[jira] Resolved: (TOMAHAWK-537) commandLin in table does not work

     [ http://issues.apache.org/jira/browse/TOMAHAWK-537?page=all ]

Michael Lipp resolved TOMAHAWK-537.
-----------------------------------

    Resolution: Invalid

OK, it has turned out to be my fault. Eventually, I looked what the JavaScript console says and found that the "onClick" script is abandoned because function "getScrolling" is not defined. And with this information I could find that I need to configure an ExtensionsFilter.

Maybe the necessity to add this filter when moving from 1.1.1 to 1.1.3 should have deserved a more prominent notice on the project's home page.

> commandLin in table does not work
> ---------------------------------
>
>                 Key: TOMAHAWK-537
>                 URL: http://issues.apache.org/jira/browse/TOMAHAWK-537
>             Project: MyFaces Tomahawk
>          Issue Type: Bug
>    Affects Versions: 1.1.3
>            Reporter: Michael Lipp
>
> As simple as that: put a commandlink in a dataTable, click on it, and nothing happens (well, it may be that the page is refreshed, i'm not sure, if then it happens too quickly, but maybe even that doesn't happen because the URL displayed ends with a '#', isn't that a local jump?).
> I have observed this after upgrading to 1.1.3 -- everything worked perfectly when i used 1.1.1. And, yes, I have a <h:form> around everything.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira