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.