[
https://issues.apache.org/jira/browse/TAPESTRY-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-1323.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.3
Assignee: Howard M. Lewis Ship
... and it's automatic; it applies to any mapped configuration where the key
type is java.lang.String.
> Support caseless mapped service configurations
> -----------------------------------------------
>
> Key: TAPESTRY-1323
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1323
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-ioc
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assigned To: Howard M. Lewis Ship
> Fix For: 5.0.3
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]