[
https://issues.apache.org/jira/browse/TRINIDAD-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587159#action_12587159
]
Wolfgang Chico Toepfer commented on TRINIDAD-989:
-------------------------------------------------
Here's a workaround for those who still want to work with this component:
1) Use
<tr:inputListOfValues
valueChangeListener="#{ctrl.handleValueChange}"
autoSubmit="false"
immediate="true" .. />
2) In ctrl add
public void handleValueChange(final ValueChangeEvent event){
// set the data to pass to the dialog here since a listener
always runs before the dialog
}
That's it.
> InputListOfValues limitations
> -----------------------------
>
> Key: TRINIDAD-989
> URL: https://issues.apache.org/jira/browse/TRINIDAD-989
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.0.6-core
> Reporter: Tomas Havelka
>
> It should be good to improve and fix component inputListOfValues behavior,
> because some limitations make it unusable. Below is list of these limitations:
> 1) Not supported LaunchListener - in many cases it is recommended to
> initialize LOV dialog with several parameters
> 2) Not used convertor for returned values - when value is returned from
> dialog, component does not use convertor to convert it to String value; it
> simply calls toString() method on that value to apply it to component
> 3) Custom ReturnListener problem - when custom ReturnListener is registered,
> it cannot manipulate with component value; it could be useful to process some
> additional logic on return value before setting it to component
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
