[richfaces-issues] [JBoss JIRA] (RF-11332) Improve AutoComplete component to support Object values separate from AutoCompleteinput field

Brian Leathem (Updated) (JIRA) jira-events at lists.jboss.org
Tue Oct 4 21:50:16 EDT 2011


     [ https://issues.jboss.org/browse/RF-11332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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)

    
> 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
>             Fix For: 4.1.0.Tracking
>
>
> {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 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

        


More information about the richfaces-issues mailing list