[jira] [Closed] (CHAIN-63) Replace Context with Map

["Simone Tripodi (Closed) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CHAIN-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simone Tripodi closed CHAIN-63.
-------------------------------

       Resolution: Duplicate
    Fix Version/s: 2.0
         Assignee: Simone Tripodi

This is a duplicate of CHAIN-58
                
> Replace Context with Map<String, ? extends Object>
> --------------------------------------------------
>
>                 Key: CHAIN-63
>                 URL: https://issues.apache.org/jira/browse/CHAIN-63
>             Project: Commons Chain
>          Issue Type: Improvement
>    Affects Versions: 2.0
>            Reporter: Ales Dolecek
>            Assignee: Simone Tripodi
>            Priority: Minor
>             Fix For: 2.0
>
>
> Hello,
>   I always wandered why you *force* chain users to use the Context interface which adds nothing over Map. I would understand that if the Context would not inherit from map and only required
> Object put(String, Object)
> Object get(String)
> But since Context itself IS Map then you gain nothing while disallowing use of Map implementations. I know that sou suggest that Context shall implement "Attribute-Property Transparency" but it is only recomendation and is not forced by commons chains anyway.
> And if you define execute like
> Object execute(Map<String, ? extends Object> context)
> it can still accept Context instances and all its subclasses.
> The downside is that you would have to give up the retrieve method introduced to Context. And BTW the Context imposes hard restriction see my other bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira