[
https://issues.jboss.org/browse/RF-13662?page=com.atlassian.jira.plugin.s...
]
Martin Höller commented on RF-13662:
------------------------------------
I'd say providing a selection-attribute simplifies component usage instead of
complicating it.
selectItem/unselectItem (and maybe a selectionChange-event) are welcome but they would
still complicate my use-case compared with the selection-attribute: I'd have to use an
additional a4j:jsFunction to propagate the client-side changes to the server.
So while I understand your arguing on keeping component API small/simple, I still suggest
providing available informations to the user. The user doesn't have to use the
selection-attribute if he doesn't need it. So usage would be the same in most cases.
<rich:orderingList> doesn't provide selection
---------------------------------------------
Key: RF-13662
URL:
https://issues.jboss.org/browse/RF-13662
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: component-selects
Affects Versions: 4.3.7
Reporter: Martin Höller
Labels: waiting_on_user
In RichFaces 3.x the <rich:orderingList> component had a selection-Attribute. In
RichFaces 4.x this is currently not supported and thus there is not way to obtain the
selected entries. Please bring back this useful feature!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)