Tapestry
  1. Tapestry
  2. TAPESTRY-853

Palette silently fails when bound to wrong collection type

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.2
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      OSX

      Description

      After more time than I would like to publicly admin, I finally figured out why my palette was not working as expected. I was binding my component to a java.util.Set and while it would appear to work, the set that the palette was bound to never get updated.

      I think this may be the fault of ognl, but wanted to share the pain that I experienced.

        Activity

        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12568087 ] jira [ 12591184 ]
        Mark Thomas made changes -
        Workflow jira [ 12346561 ] Default workflow, editable Closed status [ 12568087 ]
        Jesse Kuhnert made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee Jesse Kuhnert [ jkuhnert ]
        Resolution Fixed [ 1 ]
        Jesse Kuhnert made changes -
        Field Original Value New Value
        Fix Version/s 4.1.2 [ 12312202 ]
        phillip rhodes created issue -

          People

          • Assignee:
            Jesse Kuhnert
            Reporter:
            phillip rhodes
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development