[
https://issues.apache.org/jira/browse/TRINIDAD-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570202#action_12570202
]
Tomas Havelka commented on TRINIDAD-957:
----------------------------------------
I know that, but let me present what I mean in follwing example.
Suppose, that I have managed bean with several common methods for managing
tables (tree tables, trees) such as removeSelectedRows, insertRow,
archiveSelectedRows etc. Some of this methods works with table selection
usually iterating through its RowKySet, sets table row key and perfoms
specified action on that table row. It works well for table, but tree nor
treeTable have not the same predecessor neither the same interface implemented
so different set of those methods must be implemented for table and tree
separately, but with the same functionality.
Tom
> Common interface for selective components
> -----------------------------------------
>
> Key: TRINIDAD-957
> URL: https://issues.apache.org/jira/browse/TRINIDAD-957
> Project: MyFaces Trinidad
> Issue Type: Wish
> Components: Components
> Affects Versions: 1.0.7-core
> Reporter: Tomas Havelka
> Priority: Minor
>
> It would be nice, if components like UIXTable, UIXTree and other model-based
> selective components had implement any common interface like
> SelectableComponent to tell, that component has methods getSelectedRowKeys,
> getSelectedRowData etc. to manipulate with selections made to that component.
> Maybe more interfaces to group some components functionality together could
> be provided.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
