[
https://issues.apache.org/jira/browse/LABS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631997#action_12631997
]
Simone Gianni commented on LABS-155:
------------------------------------
Added .isCollection to PropertyInfo?, and also added .getCollectionClass which
tries to determine out of the generic declaration what is the type of the
collection.
If it does not manage to determine it, currently it is not available. It could
anyway be determined by other informations (like a @OneToMany? annotation), but
that is out of the scope right now.
Now :
* the handler should be able to deal with reading and writing collection
entries
* the handler should be able to deal with addition and removal of elements.
* the form should be able to bind to elements of the collection
How to do this if collection is not a list (or does not have some kind of
"index")? Using hashCode as a key (if the hashCode methods in not implemented
could yeld unpredictable results)? Using the database id if present? Using the
convertor value for it?
> Provide infrastructure for Collections and Arrays properties
> ------------------------------------------------------------
>
> Key: LABS-155
> URL: https://issues.apache.org/jira/browse/LABS-155
> Project: Labs
> Issue Type: Wish
> Components: Magma
> Reporter: Simone Gianni
> Assignee: Simone Gianni
>
> Currently, there is no special treatment for them, while in beansview, in
> validation and in conversion its absolutely needed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
