Tapestry
  1. Tapestry
  2. TAPESTRY-1323

Support caseless mapped service configurations

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0
    • Fix Version/s: 5.0.3
    • Component/s: tapestry-ioc
    • Labels:
      None

      Description

      Many service configurations map a string to a some object. With the recent push towards caselessness, the raw Map<String,Object> is often converted to a CaseInsensitiveMap.

      This has two problems:
      1) There may be collisions in the raw map that are not noticed (i.e., "mybean" vs. "MyBean").
      2) There's the extra code required to create and CIM and load it from the configuration Map.

      tapestry-ioc should recognize builder method parameters of type CaseInsensitiveMap and treat them accordingly. Contribution methods should still see a MappedConfiguration parameter.

        Activity

        Hide
        Howard M. Lewis Ship added a comment -

        ... and it's automatic; it applies to any mapped configuration where the key type is java.lang.String.

        Show
        Howard M. Lewis Ship added a comment - ... and it's automatic; it applies to any mapped configuration where the key type is java.lang.String.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development