[
https://issues.jboss.org/browse/RFPL-1723?page=com.atlassian.jira.plugin....
]
Ján Jamrich updated RFPL-1723:
------------------------------
Description:
Autocomplete behave really strange in Metamer. There is couple of problems:
1. updating any attribute value causes not updating value in output panel if pick some
value from suggestions
2. if value is typed and event blur fired, value from autocomplete occurs in output panel,
but in log appears error telling that javax.faces.FacesException: Method not found:
org.richfaces.tests.metamer.bean.RichBean(a)197b851.changeEventListener()
was:
Autocomplete behave really strange in Metamer. There is couple of problems:
1. updating any attribute value causes not updating value in output panel if pick some
value from suggestions
2. if value is typed and event blur fired, value from autocomplete occurs in output panel,
but in log appears error telling that javax.faces.FacesException: Method not found:
org.richfaces.tests.metamer.bean.RichBean(a)197b851.changeEventListener()
3. Ajax behavior added into autocomplete is invoked as expected, but then is overriden by
another call, so in phase logger is call for valueChangeListener missing.
Steps to Reproduce:
Open page faces/components/a4jAjax/eventHandlers.xhtml,
faces/components/a4jAjax/defaultEventHandlers.xhtml and
faces/components/richAutocomplete/autocomplete.xhtml to simulate this.
Changing attribute value - problem description:
1. open page with autocomplete faces/components/richAutocomplete/autocomplete.xhtml
2. start typing "ala" - suggestions such as "Alaska, Alabama"
appears
3. pick some item (Alaska).
4. value Alaska appears in output panel
5. now change some attribute value (according to my observation doesn't matter which
attribute). Change @selectFirst=true
6. start typing into autocomplete again. Let say "c" and wait for suggestions
(California, Collorada, Connecticut)
7. pick some value from suggestions. In phase logger appears in phase 3 this record: *1
value changed: Alaska -> (this indicating that value from bean was removed). In output
panel last value (Alaska) disappear as well.
8. click somewhere on page. Page get rerendered, and in log appears following error (see
attachment for full stack trace)
WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0.0.0.0-8080-1)
Method not found: org.richfaces.tests.metamer.bean.RichBean(a)1aaa6f3.changeEventListener():
javax.el.MethodNotFoundException: Method not found:
org.richfaces.tests.metamer.bean.RichBean(a)1aaa6f3.changeEventListener()
9. In phase logger disappears record with valueChangeListener output (*1 value changed
Alaska -> ), and output panel is still empty. But you just saw in previous step that
valueChangeListener mentioned in log really exists since wrote record to phase logger.
was:Open page faces/components/a4jAjax/eventHandlers.xhtml,
faces/components/a4jAjax/defaultEventHandlers.xhtml and
faces/components/richAutocomplete/autocomplete.xhtml to simulate this.
Metamer: rich:autocomplete: strange behavior on attribute value
change and event listener invoking
--------------------------------------------------------------------------------------------------
Key: RFPL-1723
URL:
https://issues.jboss.org/browse/RFPL-1723
Project: RichFaces Planning
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.1.0.Milestone3
Environment: RichFaces 4.1.0.20111011-M3 r.
Metamer 4.1.0.20111011-M3 r.22776
Mojarra 2.0.4-b09-jbossorg-4
JBoss Web 7.0.1.Final
Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
Firefox 8.0 @ Linux i686, Internet Explorer 7 @ win32
Reporter: Ján Jamrich
Assignee: Ján Jamrich
Autocomplete behave really strange in Metamer. There is couple of problems:
1. updating any attribute value causes not updating value in output panel if pick some
value from suggestions
2. if value is typed and event blur fired, value from autocomplete occurs in output
panel, but in log appears error telling that javax.faces.FacesException: Method not found:
org.richfaces.tests.metamer.bean.RichBean(a)197b851.changeEventListener()
--
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