Details
-
Type:
Feature Request
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 4.1.0.Milestone1
-
Fix Version/s: None
-
Component/s: component-input
-
Labels:None
-
Sprint:4.5.0.Beta1 - Upgrade Sprint
-
Forum Reference:
Description
<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.
Gliffy Diagrams
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
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.
Cody Lerum
added a comment - - edited 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. Also I need to be able to observe an on change event with f:ajax so that I can have the value pushed to the backing bean via ajax and rerender parts of the page.
Cody Lerum
added a comment - Also I need to be able to observe an on change event with f:ajax so that I can have the value pushed to the backing bean via ajax and rerender parts of the page. http://community.jboss.org/message/621988#621988 - added some comments.
Ilya Shaikovsky
added a comment - http://community.jboss.org/message/621988#621988 - added some comments. Something like this - http://xoxco.com/clickable/jquery-tags-input but with support for only a single Object value as well as multiple Object values.
Cody Lerum
added a comment - Something like this - http://xoxco.com/clickable/jquery-tags-input but with support for only a single Object value as well as multiple Object values. New issue created to track adding autocomplete functionality to the rich:select component RF-11453
Brian Leathem
added a comment - New issue created to track adding autocomplete functionality to the rich:select component RF-11453 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.
Brian Leathem
added a comment - 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. On further investigation, it seems that adding autocomplete functionality to the select component is simpler.
Brian Leathem
added a comment - On further investigation, it seems that adding autocomplete functionality to the select component is simpler. 
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.