[
https://issues.jboss.org/browse/RF-11332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Leathem reopened RF-11332:
--------------------------------
>From a pragmatic perspective, adding an extra hidden input to the autocomplete
>for use with the converter is likely the _simplest_ solution for the given use
>case. As such I'm re-opening this issue. If after an initial PoC it does not
>prove to be a simpler approach than the select-based RF-11453 we can re-close
>the issue.
> Improve AutoComplete component to support Object values separate from
> AutoCompleteinput field
> ---------------------------------------------------------------------------------------------
>
> Key: RF-11332
> URL: https://issues.jboss.org/browse/RF-11332
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.1.0.Milestone1
> Reporter: Cody Lerum
> Assignee: Brian Leathem
>
> {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.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
