Labs
  1. Labs
  2. LABS-155

BEANS: Provide infrastructure for Collections and Arrays properties

    Details

    • Type: Wish Wish
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: Current
    • Fix Version/s: Future
    • Component/s: Magma
    • Labels:
      None

      Description

      Currently, there is no special treatment for them, while in beansview, in validation and in conversion its absolutely needed.

        Activity

        Simone Gianni made changes -
        Affects Version/s Current [ 12313487 ]
        Fix Version/s Future [ 12313489 ]
        Simone Gianni made changes -
        Field Original Value New Value
        Summary Provide infrastructure for Collections and Arrays properties BEANS: Provide infrastructure for Collections and Arrays properties
        Hide
        Simone Gianni added a comment -

        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?

        Show
        Simone Gianni added a comment - 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?
        Simone Gianni created issue -

          People

          • Assignee:
            Simone Gianni
            Reporter:
            Simone Gianni
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development