[
https://issues.jboss.org/browse/RF-11422?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-11422 at 10/7/11 1:08 PM:
----------------------------------------------------------
Both functions are serving same purpose.
We need to make clarity about @filterFunction and @clientFilterFunction.
It means look at available samples and docs.
From my point of view, @filterFunction is preferable to stay.
was (Author: lfryc):
We need to make clarity about @filterFunction and @clientFilterFunction.
It means look at available samples and docs.
From my point of view, @filterFunction is preferable to stay.
rich:autocomplete: @filterFunction doesn't work
-----------------------------------------------
Key: RF-11422
URL:
https://issues.jboss.org/browse/RF-11422
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: cdk
Affects Versions: 4.1.0.Milestone2
Environment: RichFaces 4.1.0-SNAPSHOT
r.5fe1b72ff67eae7dfb1b1bb22f303576ebdcf6b5
Metamer 4.1.0-SNAPSHOT r.unknown
Mojarra 2.1.2-FCS
Apache Tomcat 7.0.19
Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
Mozilla/5.0 (X11; Linux i686; rv:7.0) Gecko/20100101 Firefox/7.0
Reporter: Ján Jamrich
Assignee: Lukáš Fryč
Fix For: 4.1.0.Tracking
@filterFunction is not working in Metamer demo. Seems that @clientFilterFunction value
override @filterFunction value in Autocomplete component renderer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira