Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.2
    • Fix Version/s: 2.2
    • Component/s: Components/Renderers
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      479
    • Status Whiteboard:
      Hide

      cat2 javadoc size_medium importance_large draft

      Show
      cat2 javadoc size_medium importance_large draft

      Description

      The root of the Java collections class structure is java.util.Collection, yet
      this interface is not supported in the UIData family of components. Instead,
      developers are forced to use a List or wrap their collection in a custom
      DataModel implementation (which is what Seam does). The impedance mismatch is
      introduced by the fact that java.util.Set is likely the most common association
      mapping in ORM. Since the UIData model and ORM go hand-in-hand, there should be
      support for java.util.Set (and preferably java.util.Collection) in UIData.
      Granted, only a java.util.List can be accessed by index, which is why it would
      be acceptable to wrap any other collection in a List implementation internally.
      Basically, the developer should not have to care that they are creating a data
      table from a Set vs a List. This is an area where the JSF abstract just bleeds.

        Issue Links

          Activity

          Hide
          Raj added a comment -

          This issue has been marked as resolved but, what about the fix for UIRepeat ? Is there a separate issue for that ?

          Show
          Raj added a comment - This issue has been marked as resolved but, what about the fix for UIRepeat ? Is there a separate issue for that ?
          Hide
          bohl_-. added a comment -

          Sorry to wake this old thread, but what about Iterable? Google's fantastic guava library is based on Iterable, not Collection. When using guava in JSF beans you still have to wrap each Iterable with ImmutableList#copyOf. Should a seperate task be created for that?

          Show
          bohl_-. added a comment - Sorry to wake this old thread, but what about Iterable? Google's fantastic guava library is based on Iterable, not Collection. When using guava in JSF beans you still have to wrap each Iterable with ImmutableList#copyOf. Should a seperate task be created for that?
          Hide
          Ed Burns added a comment -

          Sorry to wake this old thread, but what about Iterable? Google's fantastic guava library is based on Iterable, not Collection. When using guava in JSF beans you still have to wrap each Iterable with ImmutableList#copyOf. Should a seperate task be created for that?

          Yes, please, and it will not make JSF 2.2.

          This issue has been marked as resolved but, what about the fix for UIRepeat ? Is there a separate issue for that ?

          Please file an issue, and it will not make JSF 2.2.

          Show
          Ed Burns added a comment - Sorry to wake this old thread, but what about Iterable? Google's fantastic guava library is based on Iterable, not Collection. When using guava in JSF beans you still have to wrap each Iterable with ImmutableList#copyOf. Should a seperate task be created for that? Yes, please, and it will not make JSF 2.2. This issue has been marked as resolved but, what about the fix for UIRepeat ? Is there a separate issue for that ? Please file an issue, and it will not make JSF 2.2.
          Hide
          Darious3 added a comment -

          Please file an issue

          What about using JAVASERVERFACES_SPEC_PUBLIC-1103 for this?

          and it will not make JSF 2.2.

          At this point I don't think anyone assumes that any new suggestions will still make it in JSF 2.2, but what about making some public announcement about this? I.e. that new suggestions are still welcome, but will be considered for JSF 2.3 at the earliest.

          Show
          Darious3 added a comment - Please file an issue What about using JAVASERVERFACES_SPEC_PUBLIC-1103 for this? and it will not make JSF 2.2. At this point I don't think anyone assumes that any new suggestions will still make it in JSF 2.2, but what about making some public announcement about this? I.e. that new suggestions are still welcome, but will be considered for JSF 2.3 at the earliest.
          Hide
          Manfred Riem added a comment -

          Closing resolved issue out

          Show
          Manfred Riem added a comment - Closing resolved issue out

            People

            • Assignee:
              Ed Burns
              Reporter:
              pmuir
            • Votes:
              21 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Time Spent - 1 hour, 16 minutes Remaining Estimate - 3 days, 23 hours, 30 minutes
                3d 23h 30m
                Logged:
                Time Spent - 1 hour, 16 minutes Remaining Estimate - 3 days, 23 hours, 30 minutes
                1h 16m