[ https://issues.jboss.org/browse/RF-11332?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11332: ------------------------------- Assignee: Brian Leathem Fix Version/s: 4.1.0.Tracking Component/s: component-input Forum Reference: http://community.jboss.org/thread/170992?tstart=30 (was: http://community.jboss.org/thread/170992?tstart=30) I haven't yet looked at the implementation, but it seems to me that what is required is to have another "hidden" input that holds the submitted value. The visible inputText would hold a label for the value. We would then need a new attribute valueLabel, that would be of the form #{var.myLabel}. The value that goes into the hidden input should be the string returned from the converter, so it can be converted back to an object on form submission. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11332?page=com.atlassian.jira.plugin.s... ] Cody Lerum edited comment on RF-11332 at 8/19/11 12:19 AM: ----------------------------------------------------------- Primefaces 2.2 does it like this <p:autoComplete value="#{autoCompleteBean.selectedPlayer}" completeMethod="#{autoCompleteBean.completePlayer}" var="player" itemLabel="#{player.name}" itemValue="#{player}" converter="player"/> However there appears to be issues trying to observe on change events. was (Author: clerum): Primefaces 2.2 does it like this what I would like to see <p:autoComplete value="#{autoCompleteBean.selectedPlayer}" completeMethod="#{autoCompleteBean.completePlayer}" var="player" itemLabel="#{player.name}" itemValue="#{player}" converter="player"/> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11332?page=com.atlassian.jira.plugin.s... ] Ilya Shaikovsky commented on RF-11332: -------------------------------------- http://community.jboss.org/message/621988#621988 - added some comments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11332?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11332: ------------------------------- Description: {code} <rich:autocomplete id="client" value="#{newService.client}" autocompleteMethod="#{entitySearch.appEntityClients}" var="_a" fetchValue="#{_a}"> <h:outputText value="#{_a.name}" /> </rich:autocomplete> {code} Given the above code the fetchValue which is placed in the generated inputText box is what is actually submitted with the form. To support POJO selects what is needed is to have a value and a valueLabel so that the fetchValue can be displayed to the user but the acutal converted object value is submitted to the form. was: <rich:autocomplete id="client" value="#{newService.client}" autocompleteMethod="#{entitySearch.appEntityClients}" var="_a" fetchValue="#{_a}"> <h:outputText value="#{_a.name}" /> </rich:autocomplete> Given the above code the fetchValue which is placed in the generated inputText box is what is actually submitted with the form. To support POJO selects what is needed is to have a value and a valueLabel so that the fetchValue can be displayed to the user but the acutal converted object value is submitted to the form. Forum Reference: http://community.jboss.org/thread/170992?tstart=30 (was: http://community.jboss.org/thread/170992?tstart=30) -- 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